Scan all detected MCP configuration files (Claude Desktop and Cursor) for security vulnerabilities in a single operation.
AI agents call audit_all_configs to retrieve information from Agent Audit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and analyzes configuration files to detect vulnerabilities. While it operates on security-sensitive data, the action itself is passive and non-destructive—it gathers information about the configuration landscape rather than modifying systems, executing code, or deleting data. The scanning operation has no side effects on the systems being audited.
From the tool's definition Tool description states it 'scan[s]' MCP configuration files for security vulnerabilities. The verb 'scan' and the context of a security audit tool indicate data retrieval and analysis without modification.
Attacks that exploit this kind of access
Scan all detected MCP configuration files (Claude Desktop and Cursor) for security vulnerabilities in a single operation. It is categorised as a Read tool in the Agent Audit MCP Server, which means it retrieves data without modifying state.
Register the Agent Audit MCP server in PolicyLayer and add a rule for audit_all_configs: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Agent Audit. Nothing to install.
audit_all_configs is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the audit_all_configs rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for audit_all_configs. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
audit_all_configs is provided by the Agent Audit MCP server (piiiico/agent-audit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →