Soft-delete a topic. This action is irreversible through the API.
AI agents call delete_topic to permanently remove resources in Peecai — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Despite being a 'soft-delete' (logical deletion rather than physical removal), the action is documented as irreversible through the API, meaning it cannot be undone by normal API operations. This makes it a destructive action with significant impact on data availability. An AI agent with access to this tool could permanently remove topics without recovery options, warranting a high severity classification.
From the tool's definition Tool description explicitly states 'Soft-delete a topic' and 'This action is irreversible through the API.' The term 'irreversible' combined with 'delete' operation places this in the Destructive category.
Attacks that exploit this kind of access
Soft-delete a topic. This action is irreversible through the API. It is categorised as a Destructive tool in the Peecai MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Peecai MCP server in PolicyLayer and add a rule for delete_topic: 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 Peecai. Nothing to install.
delete_topic 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_topic 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_topic. 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_topic is provided by the Peecai MCP server (mcp-server-peecai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →