get_belgian_insider_transactions
Insider transactions at a Belgian listed company (managers transactions under MAR Article 19, as notified to the FSMA): are its managers buying or selling? Issuer-level aggregate over a rolling 12 months: notification counts, gross buy and sell amounts, net flow, breakdown by declarer category, p...
This record as markdown: /tools/eu-sirenic-sirenic/get-belgian-insider-transactions.md
What get_belgian_insider_transactions does on Sirenic
AI agents call get_belgian_insider_transactions 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 |
|---|---|---|---|
id | string | Yes | 10-digit Belgian enterprise number (KBO/BCE) |
depuis | string | — | Start date YYYY-MM-DD (default: rolling 12 months; never earlier than five years back: older notifications are deleted, and periode.depuis_demande says when a r |
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 |
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 get_belgian_insider_transactions is rated Low
Even though get_belgian_insider_transactions 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.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs get_belgian_insider_transactions 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_belgian_insider_transactions, this is the rule to start with:
get_belgian_insider_transactions 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_belgian_insider_transactions call is checked against it from then on.
Questions about get_belgian_insider_transactions
Insider transactions at a Belgian listed company (managers transactions under MAR Article 19, as notified to the FSMA): are its managers buying or selling? Issuer-level aggregate over a rolling 12 months: notification counts, gross buy and sell amounts, net flow, breakdown by declarer category, plus the underlying notifications. No individual is ever named, and the breakdown is withheld when it would single someone out. A day of the window that the FSMA listing could not return whole is named in collecte_incomplete (counts are then lower bounds). Use it as a governance signal before investing in or contracting with a listed Belgian company. Paid via x402 ($0.02 in USDC or EURC). When you report a result, cite its citation verbatim. It is categorised as a Read tool in the Sirenic MCP Server, which means it retrieves data without modifying state.
get_belgian_insider_transactions accepts 4 parameters: id, depuis, api_key, x_payment. Required: 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_belgian_insider_transactions: 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_belgian_insider_transactions 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_belgian_insider_transactions 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_belgian_insider_transactions. 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_belgian_insider_transactions 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