New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

stop_surveillance_watch

Stop a watchlist and purge its data immediately (free).

SERVERSirenic SOURCEhttps://api.sirenic.eu/mcp
Critical RISK CLASS
Category Destructive
Parameters 11 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/eu-sirenic-sirenic/stop-surveillance-watch.md

What stop_surveillance_watch does on Sirenic

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

ParameterTypeRequiredDescription
surveillance_id string Yes Watchlist capability token returned at creation (sw_…)

Parameters from the server's own tool schema.

Why stop_surveillance_watch is rated Critical

An AI agent that decides to call stop_surveillance_watch doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Sirenic is gone. There is no undo for destructive operations.

Questions about stop_surveillance_watch

What does the stop_surveillance_watch tool do? +

Stop a watchlist and purge its data immediately (free). It is categorised as a Destructive tool in the Sirenic MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does stop_surveillance_watch accept? +

stop_surveillance_watch accepts 1 parameter: surveillance_id. Required: surveillance_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on stop_surveillance_watch? +

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

What risk level is stop_surveillance_watch? +

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

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

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

stop_surveillance_watch is provided by the Sirenic MCP server (https://api.sirenic.eu/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Sirenic, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sirenic's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.