Start generating an AML risk report ASYNCHRONOUSLY for a Norwegian company. Returns immediately with a report_id and status 'pending' — the report is built in the background. Poll get_aml_report with the report_id until status is 'done' (then read score/level/factors) or 'failed'. Use this instea...
Part of the Firmaradar server.
Free to start. No card required.
AI agents invoke firmaradar_start_aml_report to trigger processes or run actions in Firmaradar. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
firmaradar_start_aml_report can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"firmaradar_start_aml_report": {
"limits": [
{
"counter": "firmaradar_start_aml_report_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Firmaradar policy for all 31 tools.
These attack patterns abuse exactly the kind of access firmaradar_start_aml_report gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Start generating an AML risk report ASYNCHRONOUSLY for a Norwegian company. Returns immediately with a report_id and status 'pending' — the report is built in the background. Poll get_aml_report with the report_id until status is 'done' (then read score/level/factors) or 'failed'. Use this instead of get_aml_score for large/complex ownership structures that may otherwise time out, or to start many screenings in parallel. Generates an auditable report stored for 60 months per Hvitvaskingsloven §35.. It is categorised as a Execute tool in the Firmaradar MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Firmaradar MCP server in PolicyLayer and add a rule for firmaradar_start_aml_report: 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_start_aml_report is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the firmaradar_start_aml_report 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_start_aml_report. 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_start_aml_report 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.
Deterministic rules across all 31 Firmaradar tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.