wavexis_lighthouse
Run a Lighthouse-style audit on a URL.
This record as markdown: /tools/wavexis-mcp/wavexis-lighthouse.md
What wavexis_lighthouse does on Pypi:wavexis
AI agents invoke wavexis_lighthouse to trigger actions in Pypi: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_lighthouse is rated High
This tool executes an automated third-party audit (Lighthouse) against a web resource. While read-like in nature (audits are observational), it triggers active external operations and resource consumption on the target URL, crosses system boundaries, and could be abused to perform reconnaissance, DOS-style repeated audits, or gather sensitive information about target sites.
From the tool's definition Tool name "wavexis_lighthouse" combined with description "Run a Lighthouse-style audit on a URL" indicates execution of an external audit/diagnostic tool against a specified URL.
Attacks that exploit this kind of access
The rule that runs wavexis_lighthouse safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pypi:wavexis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wavexis_lighthouse, this is the rule to start with:
wavexis_lighthouse 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 Pypi:wavexis, apply this rule, and every wavexis_lighthouse call is checked against it from then on.
Questions about wavexis_lighthouse
Run a Lighthouse-style audit on a URL. It is categorised as a Execute tool in the Pypi:wavexis MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pypi:wavexis MCP server in PolicyLayer and add a rule for wavexis_lighthouse: 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 Pypi:wavexis. Nothing to install.
wavexis_lighthouse 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_lighthouse 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_lighthouse. 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_lighthouse is provided by the Pypi: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 Pypi:wavexis, and thousands of servers like it.
Across the catalogue