Add a Norwegian company (by 9-digit orgnr) to the user's company-monitoring list. The user is then alerted when announcements, status changes (bankruptcy/dissolution), ownership changes or new public grants are registered for that company. New targets monitor ALL announcement categories by defaul...
AI agents use firmaradar_add_company_monitoring to create or update resources in Firmaradar — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Firmaradar environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
orgnr | string | Yes | Norwegian organisation number (9 digits) to add to monitoring. |
ip_alerts | boolean | — | Also enable IP-change alerts for this company. Default true = monitor everything. Requires the IP-monitoring add-on (ip_overvakning) on the account; without it |
Parameters from the server's own tool schema.
This tool creates or modifies user configuration state (a monitoring subscription with alert settings) without irreversible deletion or financial transactions. It is a Write operation because it persistently stores user preferences that can be changed or removed. Severity is medium because misuse could result in unwanted monitoring list pollution or alert spam, but no data loss or financial impact occurs.
From the tool's definition Tool adds a company to a monitoring list ('Add a Norwegian company...to the user's company-monitoring list') and configures alert preferences ('keep ip_alerts=true...or set ip_alerts=false'). These are reversible modifications to user monitoring preferences.
Attacks that exploit this kind of access
Add a Norwegian company (by 9-digit orgnr) to the user's company-monitoring list. The user is then alerted when announcements, status changes (bankruptcy/dissolution), ownership changes or new public grants are registered for that company. New targets monitor ALL announcement categories by default; keep ip_alerts=true (default) to also turn on IP-change alerts when the account has the IP-monitoring add-on, or set ip_alerts=false to skip them. 409 if already monitored (idempotent — no duplicate). Requires a user whose plan has Firmaovervakning enabled. Call only when the user has asked to monitor a specific company. It is categorised as a Write tool in the Firmaradar MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
firmaradar_add_company_monitoring accepts 2 parameters: orgnr, ip_alerts. Required: orgnr. The full parameter table on this page comes from the server's own tool schema.
Register the Firmaradar MCP server in PolicyLayer and add a rule for firmaradar_add_company_monitoring: 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 Firmaradar. Nothing to install.
firmaradar_add_company_monitoring 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 firmaradar_add_company_monitoring 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 firmaradar_add_company_monitoring. 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.
firmaradar_add_company_monitoring is provided by the Firmaradar MCP server (https://mcp.firmaradar.no/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →