stop_surveillance_watch
Stop a watchlist and purge its data immediately (free).
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
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.
Attacks that exploit this kind of access
The rule that runs stop_surveillance_watch safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sirenic, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stop_surveillance_watch, this is the rule to start with:
stop_surveillance_watch is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Sirenic, apply this rule, and every stop_surveillance_watch call is checked against it from then on.
Questions about stop_surveillance_watch
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.
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.
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.
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.
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.
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.
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.
Across the catalogue