This record as markdown: /tools/io-github-devopam-mcpg/prune-audit-events.md
What prune_audit_events does on Mcpg
AI agents call prune_audit_events to permanently remove resources in Mcpg, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why prune_audit_events is rated Critical
The word 'prune' strongly suggests deletion or trimming of data, and 'audit_events' refers to audit log records. Pruning audit events is typically an irreversible operation that removes historical compliance/security data.
From the tool's definition Tool name 'prune_audit_events' — 'prune' implies irreversible removal of audit log records
Attacks that exploit this kind of access
The rule that runs prune_audit_events safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcpg, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For prune_audit_events, this is the rule to start with:
prune_audit_events is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcpg, apply this rule, and every prune_audit_events call is checked against it from then on.
Questions about prune_audit_events
prune_audit_events is a destructive tool on the Mcpg MCP server. It is categorised as a Destructive tool in the Mcpg MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcpg MCP server in PolicyLayer and add a rule for prune_audit_events: 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 Mcpg. Nothing to install.
prune_audit_events is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the prune_audit_events 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 prune_audit_events. 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.
prune_audit_events is provided by the Mcpg MCP server (pypi:mcpg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcpg, and thousands of servers like it.
Across the catalogue