Cancel a pending/running task or delete a completed task. Saves credits if cancelled before completion.
AI agents call cancel_runway_task to permanently remove resources in Freshdesk — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
While cancelling a pending task is reversible, the tool's capability to delete completed tasks represents an irreversible action that cannot be undone. Deletion of existing records falls under the Destructive category, which takes precedence over Write (reversible modification). An AI agent misusing this could permanently remove task records and associated data.
From the tool's definition Tool description explicitly states it can "Cancel a pending/running task or delete a completed task." The verb "delete" combined with "completed task" indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access cancel_runway_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Freshdesk, and nothing reaches the server without passing your rules. This is the rule we recommend for cancel_runway_task:
{
"version": "1",
"default": "deny",
"hide": [
"cancel_runway_task"
]
}cancel_runway_task disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Cancel a pending/running task or delete a completed task. Saves credits if cancelled before completion. It is categorised as a Destructive tool in the Freshdesk MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Freshdesk MCP server in PolicyLayer and add a rule for cancel_runway_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 Freshdesk. Nothing to install.
cancel_runway_task is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cancel_runway_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_runway_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_runway_task is provided by the Freshdesk MCP server (@mindstone-engineering/mcp-server-freshdesk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Freshdesk, 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.
422 Freshdesk tools catalogued and risk-classified — across an index of 43,000+ MCP servers.