AI agents call get_component to retrieve information from Musea without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a data retrieval operation on a design system's component information. It returns existing data (metadata, variants, analysis, documentation) without creating, modifying, deleting, or executing any operations. It is a simple read query with no blast radius if invoked by an AI agent—the worst outcome is fetching unwanted component documentation.
From the tool's definition Tool name is 'get_component' with verb 'Get' and description states it retrieves 'full details' including 'metadata, variants, source-component analysis, palette data, documentation, and related resource URIs'.
Attacks that exploit this kind of access
Get full details of a design-system component: metadata, variants, source-component analysis, palette data, documentation, and related resource URIs. It is categorised as a Read tool in the Musea MCP Server, which means it retrieves data without modifying state.
Register the Musea 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 Musea. 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 Musea MCP server (@vizejs/musea-mcp-server). 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 →