Low Risk

search_by_category

Search components by category

How to control search_by_category ↓

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

Low Risk

Even though search_by_category 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 search_by_category gives an agent:

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

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

search_by_category 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 ResoniteLink MCP — 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 search_by_category tool do? +

Search components by category. It is categorised as a Read tool in the ResoniteLink MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_by_category? +

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

What risk level is search_by_category? +

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

Can I rate-limit search_by_category? +

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

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

search_by_category is provided by the ResoniteLink MCP server (rassi0429/resolink-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ResoniteLink MCP tool call.

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

Free to start. No card required.

24 ResoniteLink MCP 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.