audit_summary
Aggregate the audit log over a time window — total call count, error rate, the busiest tools, and a
This record as markdown: /tools/heznpc-airmcp/audit-summary.md
What audit_summary does on AirMCP
AI agents call audit_summary to retrieve information from AirMCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why audit_summary is rated Low
This tool queries and aggregates existing audit log data to produce summary statistics. It performs read-only operations on historical logs with no side effects, data modification, or destructive actions. The blast radius of misuse is minimal since it only exposes aggregate insights into system activity rather than enabling data changes or external operations.
From the tool's definition Tool name 'audit_summary' and description 'Aggregate the audit log over a time window — total call count, error rate, the busiest tools' indicates retrieval and analysis of historical audit data without modification or deletion.
Attacks that exploit this kind of access
The rule that runs audit_summary safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For audit_summary, this is the rule to start with:
audit_summary is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AirMCP, apply this rule, and every audit_summary call is checked against it from then on.
Questions about audit_summary
Aggregate the audit log over a time window — total call count, error rate, the busiest tools, and a. It is categorised as a Read tool in the AirMCP MCP Server, which means it retrieves data without modifying state.
Register the Air MCP server in PolicyLayer and add a rule for audit_summary: 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 AirMCP. Nothing to install.
audit_summary 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_summary 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_summary. 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_summary is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Air, and thousands of servers like it.
This server
Across the catalogue