AI agents call batch_contacts to retrieve information from Web Scraper without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves contact information from websites without creating, modifying, deleting, or executing arbitrary code. It is a read operation that queries multiple URLs to extract data. The parallel processing does not change the fundamental nature of the operation—data retrieval with no side effects.
From the tool's definition Tool name 'batch_contacts' and description 'Extract contacts from multiple URLs in parallel' indicate data retrieval without modification. The verb 'extract' combined with the web-scraper-server context shows this fetches contact information from web pages.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access batch_contacts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Web Scraper, and nothing reaches the server without passing your rules. This is the rule we recommend for batch_contacts:
{
"version": "1",
"default": "deny",
"tools": {
"batch_contacts": {}
}
}batch_contacts is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Extract contacts from multiple URLs in parallel. It is categorised as a Read tool in the Web Scraper MCP Server, which means it retrieves data without modifying state.
Register the Web Scraper MCP server in PolicyLayer and add a rule for batch_contacts: 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 Web Scraper. Nothing to install.
batch_contacts 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 batch_contacts 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 batch_contacts. 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.
batch_contacts is provided by the Web Scraper MCP server (imyourboyroy/webscrapertoolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Web Scraper, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
62 Web Scraper tools catalogued and risk-classified — across an index of 43,000+ MCP servers.