google / google/mcp

Security Consideration: Add Vedis Security Layer for MCP

Open
#36 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
4.6k
Forks
531
Avg merge
1m
Merged PRs (30d)
1

Description

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:

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

### Why this matters for Google MCP
As Google's MCP implementation, security is critical. Vedis can help protect users from:
- Prompt injection attacks in MCP interactions
- Accidental secret leakage in responses
- PII exposure in agent outputs

### 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!

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.