Crawl a URL and return all internal links found on the page. Returns structured JSON with data.internal_urls array. Useful for discovering pages before batch-fetching them. WHEN TO USE: Before a batch scraping job — call agentproxy_map first to discover URLs, then agentproxy_batch_fetch to scrape...
Risk signalsAccepts URL/endpoint input (url)
Part of the Bestproxy4agents server.
Free to start. No card required.
AI agents call agentproxy_map to retrieve information from Bestproxy4agents without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though agentproxy_map only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"agentproxy_map": {}
}
}See the full Bestproxy4agents policy for all 8 tools.
These attack patterns abuse exactly the kind of access agentproxy_map gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Crawl a URL and return all internal links found on the page. Returns structured JSON with data.internal_urls array. Useful for discovering pages before batch-fetching them. WHEN TO USE: Before a batch scraping job — call agentproxy_map first to discover URLs, then agentproxy_batch_fetch to scrape them. USE agentproxy_fetch INSTEAD IF: You only need the content of a single specific URL. NOTE: This is a shallow map (single page). For deep crawls, call agentproxy_map iteratively on discovered URLs.. It is categorised as a Read tool in the Bestproxy4agents MCP Server, which means it retrieves data without modifying state.
Register the Bestproxy4agents MCP server in PolicyLayer and add a rule for agentproxy_map: 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 Bestproxy4agents. Nothing to install.
agentproxy_map 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 agentproxy_map 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 agentproxy_map. 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.
agentproxy_map is provided by the Bestproxy4agents MCP server (bestproxy4agents-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Bestproxy4agents tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.