Search for existing components in the design system by name
AI agents call search_components to retrieve information from Ds Pilot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search/query operation to retrieve information about design system components. It has no capability to create, modify, delete, or execute operations. The blast radius of misuse is minimal - an AI agent could at worst perform excessive searches or retrieve component metadata, neither of which causes harm or changes system state.
From the tool's definition Tool name is 'search_components' and description states it 'Search for existing components in the design system by name' - a query operation that retrieves data without side effects.
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 Ds Pilot, 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 for existing components in the design system by name. It is categorised as a Read tool in the Ds Pilot MCP Server, which means it retrieves data without modifying state.
Register the Ds Pilot 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 Ds Pilot. 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 Ds Pilot MCP server (lyse-labs/ds-pilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ds Pilot, 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 Ds Pilot tools catalogued and risk-classified — across an index of 43,000+ MCP servers.