create_surveillance_watch
Company monitoring for France, for when the relationship OUTLASTS the check (supplier, borrower, portfolio company): create a 30, 90 or 365-day watchlist over French companies and/or directors. Sirenic checks every target DAILY (BODACC filings, status & officer changes, sanctions and AMF-blacklis...
This record as markdown: /tools/eu-sirenic-sirenic/create-surveillance-watch.md
What create_surveillance_watch does on Sirenic
AI agents use create_surveillance_watch to create or update resources in Sirenic, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sirenic environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
duree | string | — | Watch duration in days (default 30). Sets the unit price per target: 30 = $0.05, 90 = $0.135 (-10%), 365 = $0.50 (-17.8% vs the monthly rate). |
email | string | — | Optional e-mail address for digests |
cibles | string | Yes | 1-100 comma-separated targets: 9-digit SIRENs, RNA numbers (W + 9, associations — JOAFE notices) and/or dirigeant:Name entries |
api_key | string | — | Optional Sirenic API key (srn_live_…) to pay with prepaid credits instead of x402, with no wallet needed. Get one at https://api.sirenic.eu/compte?utm_source=ap |
webhook | string | — | Optional public https URL for signed event batches |
x_payment | string | — | Optional signed x402 PAYMENT-SIGNATURE header value. Omit to receive the payment quote. |
Parameters from the server's own tool schema.
Why create_surveillance_watch is rated Medium
An AI agent can call create_surveillance_watch faster than any human can review: one bad instruction and it creates or modifies resources in Sirenic by the hundred, each call as confident as the last.
Risk signalsAccepts URL/endpoint input (webhook) · Handles credentials or secrets (api_key) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs create_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 create_surveillance_watch, this is the rule to start with:
create_surveillance_watch stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 create_surveillance_watch call is checked against it from then on.
Questions about create_surveillance_watch
Company monitoring for France, for when the relationship OUTLASTS the check (supplier, borrower, portfolio company): create a 30, 90 or 365-day watchlist over French companies and/or directors. Sirenic checks every target DAILY (BODACC filings, status & officer changes, sanctions and AMF-blacklist matches, PSAN/SGP status, Seveso/ICPE changes, new French & EU procurement awards, and since 2026-09-24 commercial-court decisions newly linked to the company, event decision_tcom_rattachee; for directors: new/ended public offices, diffed only on a complete list, a name matching more companies than one page being marked mandats_partiels from creation) and delivers events via Ed25519-signed webhook and/or e-mail digest, always pollable with the returned bearer token, plus an expiry reminder 7 days ahead. No account. Paid via x402, per target AND per duration: $0.05 for 30 days, $0.135 for 90 days, $0.50 for 365 days (amount = that unit price × number of targets, so up to $50.00 for 100 targets over a year). No pro-rata refund. A full-size request quotes up to $50.00, above the $1.00 single-payment cap that x402 clients apply BY DEFAULT since @x402/core 2.23 (spendControls): raise spendControls.maxAmountPerPayment, or set spendControls: false, before signing; otherwise your own client rejects the quote without ever calling us. When you report a result, cite its citation verbatim. It is categorised as a Write tool in the Sirenic MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_surveillance_watch accepts 6 parameters: duree, email, cibles, api_key, webhook, x_payment. Required: cibles. 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 create_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.
create_surveillance_watch is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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