delete_watcher

THE RISK

Critical Risk

Why delete_watcher needs a policy

This tool irreversibly deletes a watcher resource that cannot be undone without manual recreation. Deleting a watcher stops real-time monitoring and removes its configuration entirely. While not directly damaging external data, the loss of monitoring and alert configurations constitutes a destructive action.

From the tool's definition Tool name is 'delete_watcher' and description states 'Stop and remove a watcher' — the verb 'remove' indicates irreversible deletion of a watcher configuration.

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

POLICY

How to control delete_watcher

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

policy.json

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

delete_watcher 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 LiveTap — 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 LiveTap tools

Destructive destroy_connection Destroy a connection — stops the source subscriber, cleans up the stream buffer. Execute restart_watcher Restart a stopped watcher. Write create_connection Create a data connection. MQTT: connects to a broker and subscribes to topics. WebSocket: Write create_watcher Create an expression-based watcher on a connection. The watcher evaluates structured condi Write update_watcher Update a watcher Read get_connection Get detailed status of a specific connection. Read get_watcher Get details of a specific watcher including conditions, status, match count, and config. Read get_watcher_logs Get evaluation logs from a watcher — shows MATCH, SUPPRESSED, FIELD_NOT_FOUND, and CHECKPO

All 13 LiveTap 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 LiveTap → 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_watcher

What does the delete_watcher tool do? +

Stop and remove a watcher. It is categorised as a Destructive tool in the LiveTap 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_watcher? +

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

What risk level is delete_watcher? +

delete_watcher 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_watcher? +

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

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

delete_watcher is provided by the LiveTap MCP server (livetap/livetap). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every LiveTap tool call.

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

CHECK YOUR STACK →