deletePosts
Permanently delete a post created by the authenticated user.
This record as markdown: /tools/xdevplatform-xmcp/deleteposts.md
What deletePosts does on Xdevplatform/xmcp
AI agents call deletePosts to permanently remove resources in Xdevplatform/xmcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why deletePosts is rated Critical
This tool removes data that cannot be undone. Once a post is permanently deleted, it is gone and cannot be recovered through normal means. The blast radius is limited by the constraint that only the authenticated user's own posts can be deleted, but the destructive nature of permanent deletion places it in the Destructive category, which ranks above Execute and Write.
From the tool's definition Tool name: 'deletePosts'; description: 'Permanently delete a post created by the authenticated user.' The word 'Permanently' combined with 'delete' clearly indicates an irreversible operation.
Attacks that exploit this kind of access
The rule that runs deletePosts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Xdevplatform/xmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deletePosts, this is the rule to start with:
deletePosts 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 Xdevplatform/xmcp, apply this rule, and every deletePosts call is checked against it from then on.
Questions about deletePosts
Permanently delete a post created by the authenticated user. It is categorised as a Destructive tool in the Xdevplatform/xmcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Xdevplatform/x MCP server in PolicyLayer and add a rule for deletePosts: 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 Xdevplatform/xmcp. Nothing to install.
deletePosts 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 deletePosts 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 deletePosts. 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.
deletePosts is provided by the Xdevplatform/x MCP server (xdevplatform/xmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Xdevplatform/x, and thousands of servers like it.
Across the catalogue