librecrawl_export_results
Export raw crawl JSON. For a formatted report use librecrawl_generate_report() instead.
This record as markdown: /tools/adityaarsharma-librecrawl-technical-seo-audit-mcp/librecrawl-export-results.md
What librecrawl_export_results does on Librecrawl Technical Seo Audit
AI agents call librecrawl_export_results to retrieve information from Librecrawl Technical Seo Audit without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why librecrawl_export_results is rated Low
The tool reads and exports existing crawl results as raw JSON. It has no side effects, does not modify data, and does not trigger new crawls or operations. Misuse risk is low since it only exposes already-collected SEO audit data.
From the tool's definition Export raw crawl JSON — this retrieves/exports already-collected crawl data without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs librecrawl_export_results 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_export_results, this is the rule to start with:
librecrawl_export_results 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 Librecrawl Technical Seo Audit, apply this rule, and every librecrawl_export_results call is checked against it from then on.
Questions about librecrawl_export_results
Export raw crawl JSON. For a formatted report use librecrawl_generate_report() instead. It is categorised as a Read tool in the Librecrawl Technical Seo Audit MCP Server, which means it retrieves data without modifying state.
Register the Librecrawl Technical Seo Audit MCP server in PolicyLayer and add a rule for librecrawl_export_results: 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_export_results 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 librecrawl_export_results 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_export_results. 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_export_results 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.
This server
Across the catalogue