Fetch any URL through residential proxy (2M+ IPs, 195 countries, anti-bot bypass). Returns structured JSON with ok, data.content, data.status_code, meta.latency_ms, and meta.cache_hit. WHEN TO USE: Static/HTML pages, Amazon, LinkedIn, news sites, most commercial sites. USE agentproxy_render INSTE...
Risk signalsAccepts URL/endpoint input (url)
Part of the Bestproxy4agents server.
Free to start. No card required.
AI agents call agentproxy_fetch 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_fetch 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_fetch": {}
}
}See the full Bestproxy4agents policy for all 8 tools.
These attack patterns abuse exactly the kind of access agentproxy_fetch 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.
Fetch any URL through residential proxy (2M+ IPs, 195 countries, anti-bot bypass). Returns structured JSON with ok, data.content, data.status_code, meta.latency_ms, and meta.cache_hit. WHEN TO USE: Static/HTML pages, Amazon, LinkedIn, news sites, most commercial sites. USE agentproxy_render INSTEAD IF: Page requires JavaScript to load (SPAs, React/Vue apps, dynamic feeds). USE agentproxy_extract INSTEAD IF: You need structured fields (title, price, rating) not raw content. ON FAILURE: If error.code is BOT_DETECTION_SUSPECTED → retry with agentproxy_render. If TLS_ERROR → retry with a different country parameter. CACHING: Repeated calls to the same URL+format+country are served from in-process cache (default TTL 300s). meta.cache_hit=true means no proxy credit was used. Sessions with session_id are never cached.. 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_fetch: 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_fetch 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_fetch 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_fetch. 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_fetch 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.