wavexis_perf_metrics
Get performance metrics (LCP, FCP, CLS, TTFB, DOMNodes, etc.).
This record as markdown: /tools/wavexis-mcp/wavexis-perf-metrics.md
What wavexis_perf_metrics does on Wavexis
AI agents call wavexis_perf_metrics to retrieve information from Wavexis without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why wavexis_perf_metrics is rated Low
This tool retrieves performance telemetry from the browser (Largest Contentful Paint, First Contentful Paint, Cumulative Layout Shift, Time to First Byte, DOM node counts). It is a pure read operation that queries existing metrics without modifying state, executing code, or affecting system behavior.
From the tool's definition Tool name 'wavexis_perf_metrics' and description 'Get performance metrics (LCP, FCP, CLS, TTFB, DOMNodes, etc.)' indicate retrieval of performance data with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs wavexis_perf_metrics 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_perf_metrics, this is the rule to start with:
wavexis_perf_metrics is read-only, so it stays allowed. 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_perf_metrics call is checked against it from then on.
Questions about wavexis_perf_metrics
Get performance metrics (LCP, FCP, CLS, TTFB, DOMNodes, etc.). It is categorised as a Read tool in the Wavexis MCP Server, which means it retrieves data without modifying state.
Register the Wavexis MCP server in PolicyLayer and add a rule for wavexis_perf_metrics: 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_perf_metrics 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 wavexis_perf_metrics 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_perf_metrics. 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_perf_metrics 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.
This server
Across the catalogue