Agent Security MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkA | Returns server health, uptime, version, and usage stats |
| scan_mcp_configA | Scan an MCP server configuration for security issues including dangerous commands, exposed secrets, network exposure, and container misconfigurations. Returns a risk score (0-100), issues found, and actionable recommendations. |
| detect_prompt_injectionA | Analyze text for prompt injection attempts. Detects instruction overrides, identity manipulation, system prompt extraction, data exfiltration, delimiter attacks, encoded injections, and privilege escalation. Context-aware risk scoring. |
| validate_scope_contractA | Check if an agent action complies with its scope contract. Validates tool usage against allowlists, file access against permitted paths, and boundary constraints (no_network, read_only, no_exec, no_secrets). |
| scan_secretsA | Detect leaked secrets and credentials in text or code. Identifies API keys (OpenAI, AWS, GitHub, GCP, Stripe, Slack, Telegram), JWT tokens, database connection strings, private keys, and .env patterns. All values are masked in output. |
| audit_agent_permissionsB | Audit an agent configuration for over-privileged access. Compares granted permissions against role-based expectations (researcher, analyst, developer, reviewer, orchestrator, monitor). Flags principle of least privilege violations. |
| generate_security_reportA | Generate a comprehensive security assessment report for an agent deployment. Aggregates results from config scans and permission audits into a prioritized remediation plan with OWASP LLM Top 10 compliance notes. |
| detect_tool_poisoningA | Analyze an MCP tool definition for poisoning indicators — hidden instructions in descriptions that could manipulate agent behavior. Covers OWASP Agentic Top 10 tool poisoning attack vectors. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| owasp-llm-top10 | |
| mcp-security-checklist |
TDQS
Scored across 8 tools
Each tool addresses a distinct security concern: health, config scanning, prompt injection, scope validation, secrets, permissions, reporting, and tool poisoning. No functional overlap.
All tool names follow a consistent verb_noun pattern (e.g., scan_mcp_config, detect_prompt_injection), making the set predictable and easy to navigate.
8 tools cover a comprehensive range of security operations without being excessive; each tool earns its place for the server's stated purpose.
The tool set covers all major security assessment areas for MCP agents: scanning, detection, validation, auditing, and reporting, leaving no obvious gaps.