wavexis_extension_install
Install a browser extension from a .crx or unpacked directory.
This record as markdown: /tools/wavexis-mcp/wavexis-extension-install.md
What wavexis_extension_install does on Wavexis
AI agents invoke wavexis_extension_install to trigger actions in Wavexis. 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.
Why wavexis_extension_install is rated High
Installing a browser extension executes external code within the browser environment, potentially granting broad permissions including access to all browsing data, network requests, and DOM manipulation.
From the tool's definition Install a browser extension from a .crx or unpacked directory
Attacks that exploit this kind of access
The rule that runs wavexis_extension_install safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Wavexis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wavexis_extension_install, this is the rule to start with:
wavexis_extension_install stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Wavexis, apply this rule, and every wavexis_extension_install call is checked against it from then on.
Questions about wavexis_extension_install
Install a browser extension from a .crx or unpacked directory. It is categorised as a Execute tool in the Wavexis MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Wavexis MCP server in PolicyLayer and add a rule for wavexis_extension_install: 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 Wavexis. Nothing to install.
wavexis_extension_install 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 wavexis_extension_install 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 wavexis_extension_install. 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.
wavexis_extension_install is provided by the Wavexis MCP server (MathiasPaulenko/wavexis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Wavexis, and thousands of servers like it.
Across the catalogue