Screen multiple individuals or organizations against global sanctions lists in a single batch operation. Supports up to 100 entities per batch. When to use: For bulk compliance screening during due diligence processes, onboarding multiple counterparties, or periodic re-screening of entity lists. ...
Part of the Orchestraprime server.
Free to start. No card required.
AI agents call screen_batch to retrieve information from Orchestraprime without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though screen_batch only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"screen_batch": {}
}
}See the full Orchestraprime policy for all 9 tools.
These attack patterns abuse exactly the kind of access screen_batch gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Screen multiple individuals or organizations against global sanctions lists in a single batch operation. Supports up to 100 entities per batch. When to use: For bulk compliance screening during due diligence processes, onboarding multiple counterparties, or periodic re-screening of entity lists. IMPORTANT: Results are NEVER cached and always reflect real-time data. Results should be reviewed by compliance professionals.. It is categorised as a Read tool in the Orchestraprime MCP Server, which means it retrieves data without modifying state.
Register the Orchestraprime MCP server in PolicyLayer and add a rule for screen_batch: 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 Orchestraprime. Nothing to install.
screen_batch 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 screen_batch 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_batch. 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_batch is provided by the Orchestraprime MCP server (@orchestraprime/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 Orchestraprime 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.