Activate a task (e.g. "StepSP").
AI agents invoke activate_task to trigger actions in ACM 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.
Activating a task in a process simulation environment (ACM) causes it to run, which triggers external operations and computations. This is an Execute-category action because it initiates a named task (like a setpoint step change) that can alter simulation state and drive dynamic behavior.
From the tool's definition 'Activate a task (e.g. "StepSP")' — activating a task triggers execution of a simulation task/procedure within ACM
Attacks that exploit this kind of access
Activate a task (e.g. "StepSP"). It is categorised as a Execute tool in the ACM MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ACM MCP Server MCP server in PolicyLayer and add a rule for activate_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.
activate_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 activate_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 activate_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.
activate_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →