Run comprehensive Google PageSpeed Insights analysis with Lighthouse metrics
AI agents call analyze_page_speed to retrieve information from PageSpeed Insights MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though analyze_page_speed only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Documented attack patterns abuse exactly the kind of access analyze_page_speed gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PageSpeed Insights MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for analyze_page_speed:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_page_speed": {}
}
} analyze_page_speed is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Run comprehensive Google PageSpeed Insights analysis with Lighthouse metrics. It is categorised as a Read tool in the PageSpeed Insights MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PageSpeed Insights MCP Server MCP server in PolicyLayer and add a rule for analyze_page_speed: 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 PageSpeed Insights MCP Server. Nothing to install.
analyze_page_speed 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_page_speed 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_page_speed. 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_page_speed is provided by the PageSpeed Insights MCP Server MCP server (ruslanlap/pagespeed-insights-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 PageSpeed Insights MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
16 PageSpeed Insights MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.