Cancel one or more tasks. Cancelled tasks remain in the system with status 2 but are no longer actionable.
AI agents use cancel_task to create or update resources in Ontraport MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ontraport MCP Server environment.
Cancelling tasks modifies their status (sets to status 2) but does not delete them — they remain in the system. This is a reversible state change (tasks could potentially be reactivated), making it a Write operation rather than Destructive. However, making tasks 'no longer actionable' has meaningful operational impact, warranting medium severity.
From the tool's definition 'Cancel one or more tasks. Cancelled tasks remain in the system with status 2 but are no longer actionable.'
Attacks that exploit this kind of access
Cancel one or more tasks. Cancelled tasks remain in the system with status 2 but are no longer actionable. It is categorised as a Write tool in the Ontraport MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ontraport MCP Server 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 Ontraport MCP Server. 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 Ontraport MCP Server MCP server (landonray/mcp-server). 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 →