coding_agent_stop_task
${DEPRECATED} Stop a running task.
This record as markdown: /tools/yuga-hashimoto-localant/coding-agent-stop-task.md
What coding_agent_stop_task does on LocalAnt
AI agents invoke coding_agent_stop_task to trigger actions in LocalAnt. 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.
Why coding_agent_stop_task is rated High
Stopping a running task is an Execute-category action because it triggers an external operation (process termination) whose effects depend on which task is targeted. While not destructive in the sense of data loss, it can interrupt work, leave systems in inconsistent states, or cause loss of unsaved state.
From the tool's definition Tool name 'coding_agent_stop_task' and description 'Stop a running task' indicate termination of an executing process. The description is marked DEPRECATED, which is uninformative about exact behavior.
Attacks that exploit this kind of access
The rule that runs coding_agent_stop_task safely
PolicyLayer is an MCP gateway: it sits between your AI agents and LocalAnt, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For coding_agent_stop_task, this is the rule to start with:
coding_agent_stop_task 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.
The button opens the PolicyLayer dashboard: create your workspace, connect LocalAnt, apply this rule, and every coding_agent_stop_task call is checked against it from then on.
Questions about coding_agent_stop_task
${DEPRECATED} Stop a running task. It is categorised as a Execute tool in the LocalAnt MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the LocalAnt MCP server in PolicyLayer and add a rule for coding_agent_stop_task: 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 LocalAnt. Nothing to install.
coding_agent_stop_task 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 coding_agent_stop_task 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 coding_agent_stop_task. 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.
coding_agent_stop_task is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on LocalAnt, and thousands of servers like it.
Across the catalogue