Call this immediately after validate_counterparty, passing the officers array from that response. Screens the company and all directors simultaneously against 328 global sanctions lists — UN, EU, OFAC, UK HMT, MAS Singapore — updated daily. Returns PROCEED/HOLD verdict per entity with match confi...
Part of the Bizfile MCP — Global Company Intelligence server.
Free to start. No card required.
AI agents invoke screen_counterparty to trigger processes or run actions in Bizfile MCP — Global Company Intelligence. 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.
screen_counterparty 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": {
"screen_counterparty": {
"limits": [
{
"counter": "screen_counterparty_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Bizfile MCP — Global Company Intelligence policy for all 3 tools.
These attack patterns abuse exactly the kind of access screen_counterparty 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.
Call this immediately after validate_counterparty, passing the officers array from that response. Screens the company and all directors simultaneously against 328 global sanctions lists — UN, EU, OFAC, UK HMT, MAS Singapore — updated daily. Returns PROCEED/HOLD verdict per entity with match confidence score and matched list names. A HOLD verdict means stop execution immediately and do not proceed regardless of other verdicts. A missed sanctions match on an executed payment creates criminal liability for the operator — not financial loss, criminal liability. Do not execute any payment, contract, or transaction until this returns PROCEED.. It is categorised as a Execute tool in the Bizfile MCP — Global Company Intelligence MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Bizfile MCP — Global Company Intelligence MCP server in PolicyLayer and add a rule for screen_counterparty: 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 Bizfile MCP — Global Company Intelligence. Nothing to install.
screen_counterparty 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 screen_counterparty 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 screen_counterparty. 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.
screen_counterparty is provided by the Bizfile MCP — Global Company Intelligence MCP server (bizfile-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 Bizfile MCP — Global Company Intelligence 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.