This tool provides complete information about any ${libraryName} component, including properties, design props (size, variant, etc.), attributes, configuration options, and practical implementation examples from basic usage to advanced scenarios with complete code snippets.
AI agents call get_component to retrieve information from Sdds without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and queries documentation/metadata about components in a design system library. It does not create, modify, delete, execute code, or trigger external operations. The language ('provides information', 'includes properties', 'examples') indicates read-only access to static or pre-computed component documentation.
From the tool's definition Tool description states it 'provides complete information about any component' with 'properties, design props, attributes, configuration options, and practical implementation examples' — purely informational retrieval with no modification, execution, or side…
Attacks that exploit this kind of access
This tool provides complete information about any ${libraryName} component, including properties, design props (size, variant, etc.), attributes, configuration options, and practical implementation examples from basic usage to advanced scenarios with complete code snippets. It is categorised as a Read tool in the Sdds MCP Server, which means it retrieves data without modifying state.
Register the Sdds MCP server in PolicyLayer and add a rule for get_component: 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 Sdds. Nothing to install.
get_component 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 get_component 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 get_component. 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.
get_component is provided by the Sdds MCP server (@salutejs/sdds-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →