AI agents call extract_urls to retrieve information from MCP Recon without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Without an explicit description, classification relies on: (1) the tool name indicating URL extraction, a read-only operation; (2) server context as a 'web security reconnaissance' tool focused on 'passive and active information gathering'; and (3) sibling tools being uniformly Read-category.
From the tool's definition Tool name 'extract_urls' suggests retrieving/parsing URLs from resources. No description provided, limiting specificity.
Documented attack patterns abuse exactly the kind of access extract_urls gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Recon, and nothing reaches the server without passing your rules. This is the rule we recommend for extract_urls:
{
"version": "1",
"default": "deny",
"tools": {
"extract_urls": {}
}
}extract_urls 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_urls. It is categorised as a Read tool in the MCP Recon MCP Server, which means it retrieves data without modifying state.
Register the MCP Recon MCP server in PolicyLayer and add a rule for extract_urls: 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 Recon. Nothing to install.
extract_urls 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_urls 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_urls. 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_urls is provided by the MCP Recon MCP server (sundayz-hunter/mcp_recon). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Recon, 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.
13 MCP Recon tools catalogued and risk-classified — across an index of 43,000+ MCP servers.