Low Risk

agentproxy_search

Structured web search via Google (Novada). Returns JSON with ok, data.results as array of {title, url, snippet}. No HTML parsing needed — results are pre-structured. WHEN TO USE: Finding pages by topic, factual queries, discovering URLs to then fetch. USE agentproxy_fetch INSTEAD FOR: Reading a ...

Accepts freeform code/query input (query); Single-target operation

Part of the Bestproxy4agents MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

bestproxy4agents-mcp Read Risk 2/5

AI agents call agentproxy_search 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_search 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.

io-github-novadalabs-proxy4agents-mcp.yaml
tools:
  agentproxy_search:
    rules:
      - action: allow

See the full Bestproxy4agents policy for all 8 tools.

Tool Name agentproxy_search
Category Read
Risk Level Low

Agents calling read-class tools like agentproxy_search have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the agentproxy_search tool do? +

Structured web search via Google (Novada). Returns JSON with ok, data.results as array of {title, url, snippet}. No HTML parsing needed — results are pre-structured. WHEN TO USE: Finding pages by topic, factual queries, discovering URLs to then fetch. USE agentproxy_fetch INSTEAD FOR: Reading a specific URL you already have. ON FAILURE: If error.code is PROVIDER_NOT_CONFIGURED → set NOVADA_API_KEY.. It is categorised as a Read tool in the Bestproxy4agents MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on agentproxy_search? +

Add a rule in your Intercept YAML policy under the tools section for agentproxy_search. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Bestproxy4agents MCP server.

What risk level is agentproxy_search? +

agentproxy_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit agentproxy_search? +

Yes. Add a rate_limit block to the agentproxy_search rule in your Intercept 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.

How do I block agentproxy_search completely? +

Set action: deny in the Intercept policy for agentproxy_search. 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.

What MCP server provides agentproxy_search? +

agentproxy_search is provided by the Bestproxy4agents MCP server (bestproxy4agents-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Bestproxy4agents

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.