librecrawl_pagespeed_audit_all_crawl_pages
A execute tool on the Librecrawl Technical Seo Audit MCP server.
This record as markdown: /tools/adityaarsharma-librecrawl-technical-seo-audit-mcp/librecrawl-pagespeed-audit-all-crawl-pages.md
What librecrawl_pagespeed_audit_all_crawl_pages does on Librecrawl Technical Seo Audit
AI agents invoke librecrawl_pagespeed_audit_all_crawl_pages to trigger actions in Librecrawl Technical Seo Audit. 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 librecrawl_pagespeed_audit_all_crawl_pages is rated High
Based on the tool name, this likely triggers an external PageSpeed audit operation across all pages discovered during a crawl, which constitutes executing an external operation. The sibling tools confirm this server runs crawl/audit operations. Empty description lowers confidence significantly. Severity is high because running audits across all crawled pages could involve large-scale external requests.
From the tool's definition Tool name 'librecrawl_pagespeed_audit_all_crawl_pages' suggests running a PageSpeed audit across all crawled pages; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs librecrawl_pagespeed_audit_all_crawl_pages safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Librecrawl Technical Seo Audit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For librecrawl_pagespeed_audit_all_crawl_pages, this is the rule to start with:
librecrawl_pagespeed_audit_all_crawl_pages 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 Librecrawl Technical Seo Audit, apply this rule, and every librecrawl_pagespeed_audit_all_crawl_pages call is checked against it from then on.
Questions about librecrawl_pagespeed_audit_all_crawl_pages
librecrawl_pagespeed_audit_all_crawl_pages is a execute tool on the Librecrawl Technical Seo Audit MCP server. It is categorised as a Execute tool in the Librecrawl Technical Seo Audit MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Librecrawl Technical Seo Audit MCP server in PolicyLayer and add a rule for librecrawl_pagespeed_audit_all_crawl_pages: 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 Librecrawl Technical Seo Audit. Nothing to install.
librecrawl_pagespeed_audit_all_crawl_pages 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 librecrawl_pagespeed_audit_all_crawl_pages 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 librecrawl_pagespeed_audit_all_crawl_pages. 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.
librecrawl_pagespeed_audit_all_crawl_pages is provided by the Librecrawl Technical Seo Audit MCP server (adityaarsharma/librecrawl-technical-seo-audit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Librecrawl Technical Seo Audit, and thousands of servers like it.
Across the catalogue