Highlight the Vue component.
AI agents invoke highlight-component to trigger actions in Vite Plugin Vue. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Highlighting a component triggers an external action in the browser or devtools environment (visual highlighting), which goes beyond a pure read. It causes a side effect in the UI state. It is not destructive or financial, and the blast radius is minimal — at worst it briefly changes visual rendering in a dev environment.
From the tool's definition "Highlight the Vue component" — triggers an external visual operation in the browser/devtools UI
Attacks that exploit this kind of access
Highlight the Vue component. It is categorised as a Execute tool in the Vite Plugin Vue MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Vite Plugin Vue MCP server in PolicyLayer and add a rule for highlight-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 Vite Plugin Vue. Nothing to install.
highlight-component is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the highlight-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 highlight-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.
highlight-component is provided by the Vite Plugin Vue MCP server (vite-plugin-vue-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.