Low Risk

agentic_search

agentic_search

How to control agentic_search ↓

AI agents call agentic_search to retrieve information from Relace MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Even though agentic_search only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Documented attack patterns abuse exactly the kind of access agentic_search gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Relace MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for agentic_search:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "agentic_search": {}
  }
}

agentic_search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Relace MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the agentic_search tool do? +

agentic_search. It is categorised as a Read tool in the Relace MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on agentic_search? +

Register the Relace MCP Server MCP server in PolicyLayer and add a rule for agentic_search: 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 Relace MCP Server. Nothing to install.

What risk level is agentic_search? +

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

Can I rate-limit agentic_search? +

Yes. Add a rate_limit block to the agentic_search 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.

How do I block agentic_search completely? +

Set action: deny in the PolicyLayer policy for agentic_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 agentic_search? +

agentic_search is provided by the Relace MCP Server MCP server (possible055/relace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Relace MCP Server tool call.

Deterministic rules across all 8 Relace MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

8 Relace MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.