AI agents call list_components 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 retrieves metadata about registered Vue.js design system components without creating, modifying, executing, or deleting anything. It is a straightforward read operation with minimal security risk, as it only exposes design system inventory information that is typically non-sensitive within a development context.
From the tool's definition Tool description states it 'List components' and 'Returns titles, categories, tags, status, variant names, and related resource URIs' — purely a query/retrieval operation with no modification or execution.
Attacks that exploit this kind of access
List components registered in the design system. Returns titles, categories, tags, status, variant names, 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 list_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 Musea. Nothing to install.
list_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 list_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 list_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.
list_components 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 →