stop-background-task · MCP Background Task Server MCP

WHAT IT DOES

What stop-background-task does on MCP Background Task Server

AI agents invoke stop-background-task to trigger actions in MCP Background Task Server. 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 stop-background-task needs a policy

This tool triggers external operations (process termination) whose effects cannot be trivially undone—a running build or development server interrupted mid-task could leave systems in inconsistent states, disrupt deployments, or cause client disconnects. It is more severe than Write (which creates/modifies reversibly) but falls short of Destructive (which targets data) or Financial.

From the tool's definition The tool 'stops a running background task by its name' performs a control-plane action that terminates a process.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop-background-task Rate-limited

stop-background-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": {
    "stop-background-task": {
      "limits": [
        {
          "counter": "stop-background-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 MCP Background Task Server, so you can run agents against it safely.

FAQ

Questions about stop-background-task

What does the stop-background-task tool do? +

Stops a running background task by its name. It is categorised as a Execute tool in the MCP Background Task Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on stop-background-task? +

Register the MCP Background Task Server MCP server in PolicyLayer and add a rule for stop-background-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 MCP Background Task Server. Nothing to install.

What risk level is stop-background-task? +

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

Can I rate-limit stop-background-task? +

Yes. Add a rate_limit block to the stop-background-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 stop-background-task completely? +

Set action: deny in the PolicyLayer policy for stop-background-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 stop-background-task? +

stop-background-task is provided by the MCP Background Task Server MCP server (nanoseil/mcp-bgtask). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.