Validate multiple email addresses in batch. More efficient for validating multiple emails at once.
AI agents call validate_batch to retrieve information from Zerobounce without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries an external service to validate and retrieve information about email addresses. It performs lookups that return validation results (likely status: valid, invalid, catch-all, etc.) but does not create, modify, delete, or execute arbitrary operations. The action is read-only with no side effects on the email addresses themselves or on the system.
From the tool's definition Tool name 'validate_batch' and description 'Validate multiple email addresses in batch' indicate data retrieval and validation—checking email status against ZeroBounce's database without modifying, creating, or deleting any data.
Attacks that exploit this kind of access
Validate multiple email addresses in batch. More efficient for validating multiple emails at once. It is categorised as a Read tool in the Zerobounce MCP Server, which means it retrieves data without modifying state.
Register the Zerobounce MCP server in PolicyLayer and add a rule for validate_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 Zerobounce. Nothing to install.
validate_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 validate_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 validate_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.
validate_batch is provided by the Zerobounce MCP server (@zerobounce/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
validate_batch is one line of Zerobounce's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →