Search ui-layouts components by name / key / group / tags / href.
AI agents call search_components to retrieve information from Ui Layouts without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a retrieval/query tool that searches a component database by various attributes. It has no side effects, does not execute code, does not modify data, and does not delete anything. The context of sibling tools (get_component_meta, get_docs, get_source_code) further confirms this is part of a read-only information retrieval system for a UI component library.
From the tool's definition Tool name 'search_components' and description indicate a search operation that 'Search[es] ui-layouts components by name / key / group / tags / href' with no mention of modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access search_components gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ui Layouts, and nothing reaches the server without passing your rules. This is the rule we recommend for search_components:
{
"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.
Free to start. No card required.
Search ui-layouts components by name / key / group / tags / href. It is categorised as a Read tool in the Ui Layouts MCP Server, which means it retrieves data without modifying state.
Register the Ui Layouts 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 Ui Layouts. Nothing to install.
search_components is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
search_components is provided by the Ui Layouts MCP server (ui-layouts/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ui Layouts, 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.
4 Ui Layouts tools catalogued and risk-classified — across an index of 43,000+ MCP servers.