librecrawl_get_settings
Get current crawler settings (maxUrls, maxDepth, crawlDelay, JS rendering, etc).
This record as markdown: /tools/adityaarsharma-librecrawl-technical-seo-audit-mcp/librecrawl-get-settings.md
What librecrawl_get_settings does on Librecrawl Technical Seo Audit
AI agents call librecrawl_get_settings 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_get_settings is rated Low
This tool queries and returns existing crawler configuration state. It has no side effects, does not modify data, does not execute code, and does not delete or move resources. It is a straightforward data retrieval operation with minimal blast radius if misused by an agent.
From the tool's definition Tool name 'librecrawl_get_settings' and description 'Get current crawler settings' indicate a read-only operation that retrieves configuration parameters (maxUrls, maxDepth, crawlDelay, JS rendering, etc) without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs librecrawl_get_settings 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_get_settings, this is the rule to start with:
librecrawl_get_settings 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_get_settings call is checked against it from then on.
Questions about librecrawl_get_settings
Get current crawler settings (maxUrls, maxDepth, crawlDelay, JS rendering, etc). 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_get_settings: 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_get_settings 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_get_settings 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_get_settings. 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_get_settings 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