librecrawl_full_audit_strict
A execute tool on the Librecrawl Technical Seo Audit MCP server.
This record as markdown: /tools/adityaarsharma-librecrawl-technical-seo-audit-mcp/librecrawl-full-audit-strict.md
What librecrawl_full_audit_strict does on Librecrawl Technical Seo Audit
AI agents invoke librecrawl_full_audit_strict 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_full_audit_strict is rated High
Based on the server context (technical SEO crawler that runs full audits with 50+ checks) and the tool name pattern matching sibling tools like librecrawl_audit, this tool likely executes a full site crawl/audit operation. The 'strict' suffix suggests more aggressive or comprehensive crawling behavior.
From the tool's definition Tool name contains 'audit' and 'strict', sibling tools include librecrawl_audit which runs full crawl audits; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs librecrawl_full_audit_strict 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_full_audit_strict, this is the rule to start with:
librecrawl_full_audit_strict 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_full_audit_strict call is checked against it from then on.
Questions about librecrawl_full_audit_strict
librecrawl_full_audit_strict 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_full_audit_strict: 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_full_audit_strict 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_full_audit_strict 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_full_audit_strict. 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_full_audit_strict 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