Extract contact information like emails, phones, addresses from web pages
AI agents call extract_contact_info to retrieve information from MCP Web Scrape without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data extraction and retrieval from web content without creating, modifying, deleting, or executing anything. It passively reads and parses contact information from HTML/web content. While contact information extraction raises privacy considerations, from a capability classification perspective this is a Read operation with minimal blast radius—it retrieves already-public web content.
From the tool's definition Tool name 'extract_contact_info' and description 'Extract contact information like emails, phones, addresses from web pages' indicate retrieval of publicly available data with no modification or side effects.
Documented attack patterns abuse exactly the kind of access extract_contact_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Web Scrape, and nothing reaches the server without passing your rules. This is the rule we recommend for extract_contact_info:
{
"version": "1",
"default": "deny",
"tools": {
"extract_contact_info": {}
}
}extract_contact_info 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 contact information like emails, phones, addresses from web pages. It is categorised as a Read tool in the MCP Web Scrape MCP Server, which means it retrieves data without modifying state.
Register the MCP Web Scrape MCP server in PolicyLayer and add a rule for extract_contact_info: 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 MCP Web Scrape. Nothing to install.
extract_contact_info 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 extract_contact_info 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 extract_contact_info. 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.
extract_contact_info is provided by the MCP Web Scrape MCP server (mukul975/mcp-web-scrape). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Web Scrape, 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.
48 MCP Web Scrape tools catalogued and risk-classified — across an index of 43,000+ MCP servers.