stop_task

Stop (abort) a running task.

SERVERProxmox MCP Server SOURCEgethosthewalrus/proxmox-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/gethosthewalrus-proxmox-mcp/stop-task.md

WHAT IT DOES

What stop_task does on Proxmox MCP Server

AI agents invoke stop_task to trigger actions in Proxmox MCP 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.

RISK

Why stop_task is rated High

While stopping a task is reversible in nature (unlike deletion), it is an action that triggers external operations on the Proxmox VE system. This is not a passive read operation, nor is it a data modification (Write). It qualifies as Execute because it triggers/controls an external process.

From the tool's definition The tool 'stop_task' performs an action that aborts a running task on Proxmox VE infrastructure. Stopping a task is an operational action that triggers external effects on the infrastructure (terminating whatever operation is in progress), which fits the…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs stop_task safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Proxmox MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stop_task, this is the rule to start with:

stop_task Rate-limited

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": {
    "stop_task": {
      "limits": [
        {
          "counter": "stop_task_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Proxmox MCP Server, apply this rule, and every stop_task call is checked against it from then on.

FAQ

Questions about stop_task

What does the stop_task tool do? +

Stop (abort) a running task. It is categorised as a Execute tool in the Proxmox MCP 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_task? +

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

What risk level is stop_task? +

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

Can I rate-limit stop_task? +

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

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

stop_task is provided by the Proxmox MCP Server MCP server (gethosthewalrus/proxmox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Proxmox MCP Server, and thousands of servers like it.

This server

All 286 Proxmox MCP Server tools → High-risk tools on this server →

Across the catalogue

stop_emba_scan on EMBA-MCP →stop_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →