Low Risk

alexandria_audit

Submit an agent output for causal audit — checks if the output reached the right conclusion through sound reasoning or just got lucky. Returns reasoning quality and factual grounding scores.

Part of the Alexandria MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call alexandria_audit to retrieve information from Alexandria without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though alexandria_audit only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

alexandria.yaml
tools:
  alexandria_audit:
    rules:
      - action: allow

See the full Alexandria policy for all 20 tools.

Tool Name alexandria_audit
Category Read
Risk Level Low

View all 20 tools →

Agents calling read-class tools like alexandria_audit have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the alexandria_audit tool do? +

Submit an agent output for causal audit — checks if the output reached the right conclusion through sound reasoning or just got lucky. Returns reasoning quality and factual grounding scores.. It is categorised as a Read tool in the Alexandria MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on alexandria_audit? +

Add a rule in your Intercept YAML policy under the tools section for alexandria_audit. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Alexandria MCP server.

What risk level is alexandria_audit? +

alexandria_audit is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit alexandria_audit? +

Yes. Add a rate_limit block to the alexandria_audit rule in your Intercept 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.

How do I block alexandria_audit completely? +

Set action: deny in the Intercept policy for alexandria_audit. 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.

What MCP server provides alexandria_audit? +

alexandria_audit is provided by the Alexandria MCP server (mcp-server-alexandria). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Alexandria

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.