Low Risk

get_audit_report

Get comprehensive audit report of agent work

How to control get_audit_report ↓

AI agents call get_audit_report to retrieve information from Agent MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves audit information about agent activities. It is a read-only operation that fetches data for review purposes. The verb 'get' combined with 'audit report' (a document for inspection, not modification) confirms this is a Read category tool. The severity is low because audit reports are typically informational and do not enable changes to systems or data.

From the tool's definition Tool name 'get_audit_report' and description 'Get comprehensive audit report of agent work' indicate a retrieval operation that queries and returns existing audit data without modification or side effects.

Documented attack patterns abuse exactly the kind of access get_audit_report gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Agent MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_audit_report:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_audit_report": {}
  }
}

get_audit_report is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Agent MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_audit_report tool do? +

Get comprehensive audit report of agent work. It is categorised as a Read tool in the Agent MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_audit_report? +

Register the Agent MCP server in PolicyLayer and add a rule for get_audit_report: 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 MCP. Nothing to install.

What risk level is get_audit_report? +

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

Can I rate-limit get_audit_report? +

Yes. Add a rate_limit block to the get_audit_report 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.

How do I block get_audit_report completely? +

Set action: deny in the PolicyLayer policy for get_audit_report. 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 get_audit_report? +

get_audit_report is provided by the Agent MCP server (rinadelph/agent-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Agent MCP tool call.

Deterministic rules across all 6 Agent MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

6 Agent MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.