AI agents call analyze_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 reads and queries Vue component metadata (props and emits) from source files. It has no side effects, does not execute code, create/modify/delete data, or trigger external operations. It is purely informational analysis of static component structure, making it a Read operation with low risk.
From the tool's definition Tool description states 'Statically analyze a Vue SFC to extract its props and emits' — it performs extraction and analysis without modifying data. The verbs 'analyze' and 'extract' indicate retrieval of information from existing component sources.
Attacks that exploit this kind of access
Statically analyze a Vue SFC to extract its props and emits. Accepts a Vue component path directly, or an art-file reference that resolves to the linked component source. 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 analyze_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.
analyze_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 analyze_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 analyze_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.
analyze_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 →