Low Risk

search_components

Search OriginUI components by name, category, or tags

How to control search_components ↓

What search_components does on OriginUI MCP Server

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

Low Risk

Why search_components needs a policy

Search operations retrieve and query data without modifying, deleting, or executing anything. The tool merely filters and returns component information matching the search criteria. There is no risk of data modification, execution, financial impact, or destructive operations. This is a straightforward Read category tool with minimal risk.

From the tool's definition The tool 'search_components' searches OriginUI components by name, category, or tags. The description explicitly states it performs search operations, which are read-only queries with no side effects.

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

How to control search_components

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

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

search_components 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 OriginUI 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.

Related tools and policies

Go deeper

Questions about search_components

What does the search_components tool do? +

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

How do I enforce a policy on search_components? +

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

What risk level is search_components? +

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

Can I rate-limit search_components? +

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

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

search_components is provided by the OriginUI MCP Server MCP server (kelvinchng/origin-ui-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every OriginUI MCP Server tool call.

Start from OriginUI MCP Server, 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.

7 OriginUI MCP Server 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.