Delete your own post.
AI agents call moltbook_delete_post to permanently remove resources in Moltbook MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs permanent deletion of post data. While scoped to 'own posts' (providing some mitigation), deletion is an irreversible action that destroys data. This falls into the Destructive category rather than Write because the effect cannot be reversed or recovered. The high severity reflects that an AI agent using this tool could permanently remove user-generated content from the platform.
From the tool's definition Tool description explicitly states 'Delete your own post' - delete operations irreversibly remove data and cannot be undone.
Attacks that exploit this kind of access
Delete your own post. It is categorised as a Destructive tool in the Moltbook MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Moltbook MCP Server MCP server in PolicyLayer and add a rule for moltbook_delete_post: 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 Moltbook MCP Server. Nothing to install.
moltbook_delete_post 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 moltbook_delete_post 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 moltbook_delete_post. 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.
moltbook_delete_post is provided by the Moltbook MCP Server MCP server (thebenlamm/moltbook-mcp). 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 →