cancel_task
Cancel a task in the marketplace.
This record as markdown: /tools/network-tenzro-tenzro/cancel-task.md
What cancel_task does on Tenzro Ledger MCP
AI agents use cancel_task to create or update resources in Tenzro Ledger MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tenzro Ledger MCP environment.
Why cancel_task is rated Medium
Cancelling a task modifies the state of a marketplace task (changing it from active to cancelled). While cancellation could be considered irreversible depending on implementation, task cancellation is generally a reversible state change (tasks can potentially be re-submitted) and is more akin to a Write operation than a Destructive one.
From the tool's definition Cancel a task in the marketplace
Attacks that exploit this kind of access
The rule that runs cancel_task safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tenzro Ledger MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cancel_task, this is the rule to start with:
cancel_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Tenzro Ledger MCP, apply this rule, and every cancel_task call is checked against it from then on.
Questions about cancel_task
Cancel a task in the marketplace. It is categorised as a Write tool in the Tenzro Ledger MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tenzro Ledger MCP server in PolicyLayer and add a rule for cancel_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 Tenzro Ledger MCP. Nothing to install.
cancel_task 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 cancel_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 cancel_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.
cancel_task is provided by the Tenzro Ledger MCP server (https://canton-mcp.tenzro.network/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tenzro Ledger, and thousands of servers like it.
This server
Across the catalogue