AI agents invoke fin_deepagent_cancel to trigger actions in OpenFinClaw CLI. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool terminates/cancels an active running process. It is an operational action that affects an ongoing execution — not a simple read, not a data write, and not irreversible destruction of stored data. Cancelling a run can have side effects (aborting backtests, research, or paper trading jobs in progress) but is not inherently destructive to persisted data.
From the tool's definition Cancel a running DeepAgent run
Documented attack patterns abuse exactly the kind of access fin_deepagent_cancel 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_cancel:
{
"version": "1",
"default": "deny",
"tools": {
"fin_deepagent_cancel": {
"limits": [
{
"counter": "fin_deepagent_cancel_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}fin_deepagent_cancel stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Cancel a running DeepAgent run. It is categorised as a Execute tool in the OpenFinClaw CLI MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the OpenFinClaw CLI MCP server in PolicyLayer and add a rule for fin_deepagent_cancel: 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_cancel is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the fin_deepagent_cancel 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_cancel. 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_cancel 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.