search_components

Busca componentes por nome, descrição ou funcionalidade para um caso de uso específico.

Server SigmaUI DS MCP Server ribsousa/sigmaui-ds-mcp
Category Read
Risk class Low
Parameters 00 required

What search_components does on SigmaUI DS MCP Server

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

Why search_components needs a policy

This tool retrieves and queries design system component information based on search criteria. It has no side effects, cannot modify or delete data, and does not execute code or trigger external operations. It is a straightforward informational lookup utility, consistent with other Read-category tools on this server like list_components and get_component.

From the tool's definition Tool performs search/query operations across component documentation: 'Busca componentes por nome, descrição ou funcionalidade' (searches components by name, description, or functionality). No data modification, deletion, or code execution occurs.

Questions about search_components

What does the search_components tool do? +

Busca componentes por nome, descrição ou funcionalidade para um caso de uso específico. It is categorised as a Read tool in the SigmaUI DS MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_components? +

Register the SigmaUI DS 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 SigmaUI DS 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 SigmaUI DS MCP Server MCP server (ribsousa/sigmaui-ds-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.