kill_attempt

THE RISK

Critical Risk

Why kill_attempt needs a policy

Killing/cancelling a running workflow attempt stops it permanently; any in-progress work is lost and the attempt cannot be resumed, making this an irreversible destructive action with high blast radius if misused against critical jobs.

From the tool's definition 'Request cancellation of a running attempt' — cancelling a running workflow attempt is an irreversible action that terminates execution and cannot be undone

Documented attack patterns abuse exactly the kind of access kill_attempt gives an agent:

POLICY

How to control kill_attempt

PolicyLayer is an MCP gateway — it sits between your AI agents and Treasure Data MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for kill_attempt:

policy.json

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

kill_attempt disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Treasure Data MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Treasure Data MCP Server tools

Destructive execute Execute write operations (UPDATE, DELETE, INSERT, etc.) when enable_updates=true Execute retry_attempt Retry a specific failed attempt with resume capabilities Execute retry_session Retry a failed session from the beginning or a specific task Write use_database Switch the current database context for subsequent queries Read current_database Get the current database context being used for queries Read describe_table Get column information for a specific table Read get_attempt_tasks List all tasks within an attempt with their execution status Read get_parent_segment [EXPERIMENTAL] Get details of a specific parent segment by its ID. Requires parent_segment

All 23 Treasure Data MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Treasure Data MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about kill_attempt

What does the kill_attempt tool do? +

Request cancellation of a running attempt. It is categorised as a Destructive tool in the Treasure Data MCP Server 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 kill_attempt? +

Register the Treasure Data MCP Server MCP server in PolicyLayer and add a rule for kill_attempt: 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 Treasure Data MCP Server. Nothing to install.

What risk level is kill_attempt? +

kill_attempt 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 kill_attempt? +

Yes. Add a rate_limit block to the kill_attempt 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 kill_attempt completely? +

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

kill_attempt is provided by the Treasure Data MCP Server MCP server (treasure-data/td-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Treasure Data MCP Server tool call.

Start from Treasure Data MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →