// MCP TOOL REFERENCE

run_pagespeed

Analyze one HTTP/HTTPS URL with Google PageSpeed Insights and return score summaries, Core Web Vitals, opportunities, and saved report path.

Accepts URL/endpoint input (url)

Part of the Pagespeedinsight MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@denizhosgor/pagespeedinsight-mcp Execute

// WHEN AI AGENTS USE THIS TOOL

AI agents invoke run_pagespeed to trigger processes or run actions in Pagespeedinsight. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

// WHY ENFORCE A POLICY ON RUN_PAGESPEED

run_pagespeed can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

// RECOMMENDED POLICY

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

pagespeedinsight.yaml

tools:
  run_pagespeed:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Pagespeedinsight policy for all 2 tools.

// DETAILS

Tool Name run_pagespeed

Category Execute

MCP Server Pagespeedinsight MCP Server

Risk Level High

// MORE PAGESPEEDINSIGHT TOOLS

Execute compare_pagespeed

// WHAT CAN GO WRONG

Agents calling execute-class tools like run_pagespeed have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER EXECUTE TOOLS ACROSS MCP SERVERS

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

Atv build_stake_tx Atv build_unstake_tx Acdp start_local Pentagonal pentagonal_audit Pentagonal pentagonal_compile ACR — Agent Composition Records orient_me

// IN CONTEXT OF HIGH RISK

run_pagespeed is one of the high-risk operations in Pagespeedinsight. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

// RELATED READING

// FAQ

What does the run_pagespeed tool do? +

Analyze one HTTP/HTTPS URL with Google PageSpeed Insights and return score summaries, Core Web Vitals, opportunities, and saved report path.. It is categorised as a Execute tool in the Pagespeedinsight MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_pagespeed? +

Add a rule in your Intercept YAML policy under the tools section for run_pagespeed. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Pagespeedinsight MCP server.

What risk level is run_pagespeed? +

run_pagespeed is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_pagespeed? +

Yes. Add a rate_limit block to the run_pagespeed rule in your Intercept 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.

How do I block run_pagespeed completely? +

Set action: deny in the Intercept policy for run_pagespeed. 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.

What MCP server provides run_pagespeed? +

run_pagespeed is provided by the Pagespeedinsight MCP server (@denizhosgor/pagespeedinsight-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

run_pagespeed

Let agents act without letting them run wild.