Skip to content

Security Consideration: Add Vedis Security Layer for GitHub MCP #2292

@sypherin

Description

@sypherin

I've been building AI agents with MCP and noticed a common security gap - prompt injection attacks and secret leakage.

I built Vedis to address this - it's a security layer for MCP agents that:

Detects prompt injection attempts - Blocks malicious prompts before they reach your agent
Blocks PII - Emails, phone numbers, SSNs, credit cards
Filters secrets - AWS keys, GitHub tokens, Stripe keys, JWTs, PEM certificates
Enforces tool policies - Control what tools your agents can access

How it works

One config change, zero code changes:

vedis:
  enabled: true
  block_pii: true
  block_secrets: true
  max_tokens: 1000

Why this matters for GitHub MCP

As GitHub's official MCP Server, security is critical. Vedis can help protect users from:

  • Prompt injection attacks in GitHub interactions
  • Accidental GitHub token leakage in responses
  • PII exposure in repository data access

Available at

https://vedis-4nexxwa4vq-as.a.run.app

Pricing

  • Free: Basic protection
  • $49/mo: Starter (up to 10 agents)
  • $199/mo: Pro (unlimited agents)

Would you be interested in integrating Vedis as an optional security layer? I'd be happy to contribute or provide more details.

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions