New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

check_batch

check_before_pay for up to 20 targets at once, each with the amount you would pay it. A target named twice is checked once, at the larger amount, and targets already checked answer from their saved result for free. Do not pay a target whose decision is DENY, and do not check the same targets again.

SERVERTrust SOURCE@a-identity/trust-mcp
Low RISK CLASS
Category Read
Parameters 11 required
Recommended Allowedsee the rule below
Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/a-identity-trust-mcp/check-batch.md

What check_batch does on Trust

AI agents call check_batch to retrieve information from Trust without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
targets array Yes The targets, each with what you are about to pay it in USD.

Parameters from the server's own tool schema.

Why check_batch is rated Low

Even though check_batch 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.

Questions about check_batch

What does the check_batch tool do? +

check_before_pay for up to 20 targets at once, each with the amount you would pay it. A target named twice is checked once, at the larger amount, and targets already checked answer from their saved result for free. Do not pay a target whose decision is DENY, and do not check the same targets again. It is categorised as a Read tool in the Trust MCP Server, which means it retrieves data without modifying state.

What parameters does check_batch accept? +

check_batch accepts 1 parameter: targets. Required: targets. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on check_batch? +

Register the Trust MCP server in PolicyLayer and add a rule for check_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 Trust. Nothing to install.

What risk level is check_batch? +

check_batch is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_batch? +

Yes. Add a rate_limit block to the check_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.

How do I block check_batch completely? +

Set action: deny in the PolicyLayer policy for check_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.

What MCP server provides check_batch? +

check_batch is provided by the Trust MCP server (@a-identity/trust-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Trust, and thousands of servers like it.

This server

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Trust's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.