em_cancel_task

A destructive tool on the Execution Market MCP server.

SERVERExecution Market SOURCEhttps://mcp.execution.market/mcp/

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/market-execution-execution-market/em-cancel-task.md

WHAT IT DOES

What em_cancel_task does on Execution Market

AI agents call em_cancel_task to permanently remove resources in Execution Market, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why em_cancel_task is rated Critical

Based on the name, this tool cancels a task, which is likely irreversible — cancelled tasks would release escrow, notify parties, and cannot be undone. Given the financial context (USDC payments, escrow), cancellation could also have financial implications.

From the tool's definition Tool name: em_cancel_task; description is empty. Sibling tools suggest a task marketplace with USDC payments and escrow.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs em_cancel_task safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Execution Market, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For em_cancel_task, this is the rule to start with:

em_cancel_task Hidden

em_cancel_task is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "em_cancel_task"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Execution Market, apply this rule, and every em_cancel_task call is checked against it from then on.

FAQ

Questions about em_cancel_task

What does the em_cancel_task tool do? +

em_cancel_task is a destructive tool on the Execution Market MCP server. It is categorised as a Destructive tool in the Execution Market MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on em_cancel_task? +

Register the Execution Market MCP server in PolicyLayer and add a rule for em_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 Execution Market. Nothing to install.

What risk level is em_cancel_task? +

em_cancel_task is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit em_cancel_task? +

Yes. Add a rate_limit block to the em_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.

How do I block em_cancel_task completely? +

Set action: deny in the PolicyLayer policy for em_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.

What MCP server provides em_cancel_task? +

em_cancel_task is provided by the Execution Market MCP server (https://mcp.execution.market/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Execution Market, and thousands of servers like it.

This server

All 81 Execution Market tools → Critical-risk tools on this server →

Across the catalogue

sms_cancel_scheduled on Twilio SMS MCP Server →cancel_all_orders on Lighter MCP →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →