deactivate_task · ACM MCP Server MCP: Risk & Policy

WHAT IT DOES

What deactivate_task does on ACM MCP Server

AI agents use deactivate_task to create or update resources in ACM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ACM MCP Server environment.

WHY IT NEEDS A POLICY

Why deactivate_task needs a policy

Deactivating a task changes its operational state within the ACM session but does not irreversibly delete data or destroy the task itself. It is reversible by reactivating the task. In the context of an automation server managing simulations and task states, state modifications are Write operations.

From the tool's definition The tool deactivates a task, which modifies the state of an ACM simulation task. The verb 'deactivate' indicates a state change that is reversible (can be reactivated), making it a Write operation rather than Destructive.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

deactivate_task Rate-limited

deactivate_task stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "deactivate_task": {
      "limits": [
        {
          "counter": "deactivate_task_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about deactivate_task

What does the deactivate_task tool do? +

Deactivate a task. It is categorised as a Write tool in the ACM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on deactivate_task? +

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

What risk level is deactivate_task? +

deactivate_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit deactivate_task? +

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

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

deactivate_task is provided by the ACM MCP Server MCP server (pekosann/acm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.