coding_agent_stop_task · LocalAnt MCP: Risk & Policy

WHAT IT DOES

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 IT NEEDS A POLICY

Why coding_agent_stop_task needs a policy

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

Recommended rule Ready

Verdict

coding_agent_stop_task Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "coding_agent_stop_task": {
      "limits": [
        {
          "counter": "coding_agent_stop_task_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches LocalAnt, so you can run agents against it safely.

FAQ

Questions about coding_agent_stop_task

What does the coding_agent_stop_task tool do? +

${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.

How do I enforce a policy on coding_agent_stop_task? +

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.

What risk level is coding_agent_stop_task? +

coding_agent_stop_task is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit coding_agent_stop_task? +

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.

How do I block coding_agent_stop_task completely? +

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.

What MCP server provides coding_agent_stop_task? +

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.