Delete a Threads post owned by the authenticated user.
AI agents call delete_thread to permanently remove resources in Threads MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes user-created content from Threads. Deletion is irreversible—the post cannot be recovered once deleted. This is a destructive operation that qualifies for the Destructive category.
From the tool's definition Tool name is 'delete_thread' and description states 'Delete a Threads post owned by the authenticated user.' The verb 'Delete' combined with the operation of removing a post is irreversible.
Attacks that exploit this kind of access
Delete a Threads post owned by the authenticated user. It is categorised as a Destructive tool in the Threads MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Threads MCP Server MCP server in PolicyLayer and add a rule for delete_thread: 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 Threads MCP Server. Nothing to install.
delete_thread 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_thread 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_thread. 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_thread is provided by the Threads MCP Server MCP server (poisonstefani-dev/threads-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 →