get_surveillance_watch
Status and the 100 most recent events (total and cut in listes_bornees.evenements) of a watchlist created with create_surveillance_watch. Free: the surveillance_id token IS the capability.
This record as markdown: /tools/eu-sirenic-sirenic/get-surveillance-watch.md
What get_surveillance_watch does on Sirenic
AI agents call get_surveillance_watch to retrieve information from Sirenic without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
surveillance_id | string | Yes | Token returned at creation |
Parameters from the server's own tool schema.
Why get_surveillance_watch is rated Low
Even though get_surveillance_watch only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_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 get_surveillance_watch, this is the rule to start with:
get_surveillance_watch is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sirenic, apply this rule, and every get_surveillance_watch call is checked against it from then on.
Questions about get_surveillance_watch
Status and the 100 most recent events (total and cut in listes_bornees.evenements) of a watchlist created with create_surveillance_watch. Free: the surveillance_id token IS the capability. It is categorised as a Read tool in the Sirenic MCP Server, which means it retrieves data without modifying state.
get_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 get_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.
get_surveillance_watch is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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.
This server
Across the catalogue