Extract strong README/docs claims and map them to evidence or missing evidence.
AI agents call audit_docs_claims to retrieve information from CodeAudit MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes existing documentation without creating, modifying, executing, or deleting anything. It performs document inspection and mapping, which are query/analysis operations characteristic of the Read category. The read-only nature of the entire server confirms no side effects are possible.
From the tool's definition Tool description states it 'Extract[s]' and 'map[s]' documentation claims—purely analytical operations with no modification or execution. Server is explicitly described as 'read-only' for 'inspect[ing] repositories' and 'audit[ing]'.
Attacks that exploit this kind of access
Extract strong README/docs claims and map them to evidence or missing evidence. It is categorised as a Read tool in the CodeAudit MCP MCP Server, which means it retrieves data without modifying state.
Register the CodeAudit MCP server in PolicyLayer and add a rule for audit_docs_claims: 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 CodeAudit MCP. Nothing to install.
audit_docs_claims 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_docs_claims 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_docs_claims. 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_docs_claims is provided by the CodeAudit MCP server (priyanshuchawda/codeaudit). 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 →