Low Risk

sonar_search

sonar_search

How to control sonar_search ↓

What sonar_search does on Claude TypeScript MCP Servers

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

Low Risk

Why sonar_search needs a policy

Despite the empty description, the tool name and context indicate this is a search utility that retrieves information rather than modifying, executing, or destroying data. The presence of similar search tools ('brave_local_search', 'brave_web_search') on the same development assistance server supports classification as Read.

From the tool's definition Tool name 'sonar_search' suggests a search/query operation, consistent with sibling tools 'brave_local_search' and 'brave_web_search' on the same server which retrieve data without side effects.

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

How to control sonar_search

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

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

sonar_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 Claude TypeScript MCP Servers — 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.

Related tools and policies

Go deeper

Questions about sonar_search

What does the sonar_search tool do? +

sonar_search. It is categorised as a Read tool in the Claude TypeScript MCP Servers MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on sonar_search? +

Register the Claude TypeScript MCP Servers MCP server in PolicyLayer and add a rule for sonar_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 Claude TypeScript MCP Servers. Nothing to install.

What risk level is sonar_search? +

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

Can I rate-limit sonar_search? +

Yes. Add a rate_limit block to the sonar_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 sonar_search completely? +

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

sonar_search is provided by the Claude TypeScript MCP Servers MCP server (ukkz/claude-ts-mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Claude TypeScript MCP Servers tool call.

Start from Claude TypeScript MCP Servers, 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.

84 Claude TypeScript MCP Servers tools catalogued and risk-classified — across an index of 43,000+ 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.