AI agents call delete-category to permanently remove resources in PI API MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a category cannot be undone and results in permanent data loss. This is a destructive operation affecting dashboard organization and potentially associated data. Severity is high rather than critical because the blast radius is typically limited to a single category rather than system-wide infrastructure, though the exact impact depends on how many charts or dependent resources are affected.
From the tool's definition Tool name is 'delete-category' and description states 'Delete a category'. The verb 'delete' indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access delete-category gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PI API MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete-category:
{
"version": "1",
"default": "deny",
"hide": [
"delete-category"
]
} delete-category disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a category. It is categorised as a Destructive tool in the PI API MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the PI API MCP Server MCP server in PolicyLayer and add a rule for delete-category: 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 PI API MCP Server. Nothing to install.
delete-category 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 delete-category 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 delete-category. 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.
delete-category is provided by the PI API MCP Server MCP server (mingzilla/pi-api-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PI API MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 PI API MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.