Signal that agent work was cancelled in response to a cancel control message.
AI agents use agent_cancelled to create or update resources in Conductor — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Conductor environment.
This tool writes a status update to the task tree, recording that an agent's work was cancelled. It modifies state (task status) in a reversible/trackable way rather than deleting data. The blast radius is low since it only marks a task as cancelled within the orchestration system.
From the tool's definition Signal that agent work was cancelled in response to a cancel control message.
Documented attack patterns abuse exactly the kind of access agent_cancelled gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Conductor, and nothing reaches the server without passing your rules. This is the rule we recommend for agent_cancelled:
{
"version": "1",
"default": "deny",
"tools": {
"agent_cancelled": {
"limits": [
{
"counter": "agent_cancelled_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}agent_cancelled 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.
Free to start. No card required.
Signal that agent work was cancelled in response to a cancel control message. It is categorised as a Write tool in the Conductor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Conductor MCP server in PolicyLayer and add a rule for agent_cancelled: 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 Conductor. Nothing to install.
agent_cancelled is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the agent_cancelled 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 agent_cancelled. 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.
agent_cancelled is provided by the Conductor MCP server (shannonbay/conductor). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Conductor, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 Conductor tools catalogued and risk-classified — across an index of 43,000+ MCP servers.