AgentShield — open-source security scanner for MCP servers (30 rules, offline) #13400
Replies: 1 comment
-
|
This discussion was automatically closed because the community moved to community.vercel.com/ai-sdk |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
TL;DR
I built AgentShield, an open-source security scanner for MCP servers, AI agent tools, and plugins. It statically analyzes code for backdoors, data exfiltration, prompt injection, and supply chain attacks.
With the Vercel AI SDK's MCP support, developers are connecting to third-party MCP servers — and there's currently no standard way to verify what those servers actually do before connecting.
Why This Matters for AI SDK Users
The AI SDK makes it easy to connect to MCP servers via
experimental_createMCPClient. But MCP servers run arbitrary code with access to:A malicious MCP server can look perfectly normal in its tool listing while exfiltrating data or injecting prompts behind the scenes.
What AgentShield Detects
30 rules, 100% offline, MIT licensed:
Key detections for MCP servers:
Real-World Data
Scanned 493 Dify plugins (9,862 files, 939K lines) — found 6 high-risk plugins with eval(), exec(), and reverse shell patterns published in the marketplace. Full report.
Suggestion
It would be valuable if the AI SDK ecosystem had a way to verify MCP servers before connection — perhaps as a recommended pre-check step in the docs, or as part of a registry. AgentShield could serve as the scanning layer.
GitHub: https://github.com/elliotllliu/agent-shield
Beta Was this translation helpful? Give feedback.
All reactions