interceptor_kill

THE RISK

Critical Risk

Why interceptor_kill needs a policy

Killing a process is irreversible — the process is terminated and cannot be restarted automatically. This is a destructive action with potentially high blast radius if an AI agent mistakenly kills a critical process. The tool also retrieves final output, but the dominant action is process termination.

From the tool's definition Kill a spawned process by target ID

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

POLICY

How to control interceptor_kill

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

policy.json

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

interceptor_kill 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 Proxy — 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 Proxy tools

Destructive interceptor_docker_detach Remove proxy configuration from a Docker container and clean up injected files. Destructive proxy_clear_traffic Clear all captured traffic from the buffer. Destructive proxy_delete_session Delete a recorded session from disk. Destructive proxy_remove_host_upstream Remove a per-host upstream proxy override. Destructive proxy_remove_rule Delete an interception rule. Destructive proxy_session_stop Stop persistent on-disk capture and finalize the active session. Destructive interceptor_deactivate_all Kill ALL active interceptors across all types. Emergency cleanup — stops all browser insta Destructive proxy_mobile_teardown Reverse proxy_mobile_setup: deactivate the Android target if any, stop the transparent + e

All 89 Proxy 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 Proxy → 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 interceptor_kill

What does the interceptor_kill tool do? +

Kill a spawned process by target ID. Also retrieves final stdout/stderr output. It is categorised as a Destructive tool in the Proxy 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 interceptor_kill? +

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

What risk level is interceptor_kill? +

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

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

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

interceptor_kill is provided by the Proxy MCP server (yfe404/proxy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Proxy tool call.

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

CHECK YOUR STACK →