delete_integration_file

THE RISK

Critical Risk

Why delete_integration_file needs a policy

This tool deletes files without undo capability. Even though it is scoped to 'allowed' integration worktree files and gated by patch validation logic, deletion is fundamentally irreversible. An AI agent misusing this tool could remove critical integration metadata, breaking warehouse queries and requiring manual recovery. The blast radius is high in a data platform context. Destructive takes precedence over Write.

From the tool's definition 'Delete one allowed integration worktree file' — the tool irreversibly removes data files. The qualifier 'when the failed patch proves the deletion is correct' does not prevent deletion; it is a soft control that depends on argument validity and operator…

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

POLICY

How to control delete_integration_file

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

policy.json

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

delete_integration_file 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 Ktx — 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 Ktx tools

Write record_verification_ledger Record the pre-write verification ledger required by loaded ingest skills. Call this befor Write write_integration_file Replace one allowed integration worktree file with repaired text content. Write write_repair_file Replace one allowed integration worktree file with repaired text content. Read echo_value Return the provided value as markdown. Read load_skill Load a skill to get specialized instructions. Call this when a skill listed in the system Read read_failed_patch Read the failed Git patch that could not be applied to the integration worktree. Read read_gate_error Read the artifact gate failure that must be repaired. Read read_integration_file Read one allowed file from the current integration worktree.

All 10 Ktx 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 Ktx → 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 delete_integration_file

What does the delete_integration_file tool do? +

Delete one allowed integration worktree file when the failed patch proves the deletion is correct. It is categorised as a Destructive tool in the Ktx 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 delete_integration_file? +

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

What risk level is delete_integration_file? +

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

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

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

delete_integration_file is provided by the Ktx MCP server (kaelio/ktx). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ktx tool call.

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

CHECK YOUR STACK →