threads_delete_thread
Delete a thread by ID
This record as markdown: /tools/io-github-alifanov-scopegate/threads-delete-thread.md
What threads_delete_thread does on ScopeGate
AI agents call threads_delete_thread to permanently remove resources in ScopeGate, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why threads_delete_thread is rated Critical
The tool permanently removes a thread, which is data destruction that cannot be undone. Although it targets a single thread rather than bulk data, deletion is categorized as Destructive per the classification rules.
From the tool's definition Tool name contains 'delete' and description states 'Delete a thread by ID' — this is an irreversible deletion operation.
Attacks that exploit this kind of access
The rule that runs threads_delete_thread safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For threads_delete_thread, this is the rule to start with:
threads_delete_thread 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 ScopeGate, apply this rule, and every threads_delete_thread call is checked against it from then on.
Questions about threads_delete_thread
Delete a thread by ID. It is categorised as a Destructive tool in the ScopeGate MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ScopeGate MCP server in PolicyLayer and add a rule for threads_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 ScopeGate. Nothing to install.
threads_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 threads_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 threads_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.
threads_delete_thread is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScopeGate, and thousands of servers like it.
Across the catalogue