Manage DeepAgent threads — list, create, get, or delete
AI agents call fin_deepagent_threads to permanently remove resources in OpenFinClaw CLI — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Because the tool spans multiple categories (Read for list/get, Write for create, Destructive for delete), the most severe applicable category is Destructive. Deleting threads likely irreversibly removes conversation history, associated research, strategies, or backtesting context, which could have significant impact in a quant research/trading context.
From the tool's definition 'Manage DeepAgent threads — list, create, get, or delete' — the tool explicitly supports 'delete' operations on threads
Documented attack patterns abuse exactly the kind of access fin_deepagent_threads gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenFinClaw CLI, and nothing reaches the server without passing your rules. This is the rule we recommend for fin_deepagent_threads:
{
"version": "1",
"default": "deny",
"hide": [
"fin_deepagent_threads"
]
}fin_deepagent_threads disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Manage DeepAgent threads — list, create, get, or delete. It is categorised as a Destructive tool in the OpenFinClaw CLI MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the OpenFinClaw CLI MCP server in PolicyLayer and add a rule for fin_deepagent_threads: 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 OpenFinClaw CLI. Nothing to install.
fin_deepagent_threads 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 fin_deepagent_threads 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 fin_deepagent_threads. 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.
fin_deepagent_threads is provided by the OpenFinClaw CLI MCP server (mirror29/openfinclaw-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OpenFinClaw CLI, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 OpenFinClaw CLI tools catalogued and risk-classified — across an index of 43,000+ MCP servers.