Delete specific content from the organization
AI agents call deleteOrganizationContent to permanently remove resources in Content Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible deletion operation on organization content. Deletion cannot be undone and represents permanent data loss. While not involving financial impact or arbitrary code execution, the destructive nature of data deletion makes this more severe than Write operations. High severity reflects that an agent misusing this could permanently remove important organizational content.
From the tool's definition Tool name is 'deleteOrganizationContent' and description states 'Delete specific content from the organization'. The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete specific content from the organization. It is categorised as a Destructive tool in the Content Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Content Server MCP server in PolicyLayer and add a rule for deleteOrganizationContent: 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 Content Server. Nothing to install.
deleteOrganizationContent 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 deleteOrganizationContent 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 deleteOrganizationContent. 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.
deleteOrganizationContent is provided by the Content Server MCP server (yogeshkulkarni553/rag-mcp-py). 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 →