librecrawl_merge_gsc_data
A write tool on the Librecrawl Technical Seo Audit MCP server.
This record as markdown: /tools/adityaarsharma-librecrawl-technical-seo-audit-mcp/librecrawl-merge-gsc-data.md
What librecrawl_merge_gsc_data does on Librecrawl Technical Seo Audit
AI agents use librecrawl_merge_gsc_data to create or update resources in Librecrawl Technical Seo Audit, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Librecrawl Technical Seo Audit environment.
Why librecrawl_merge_gsc_data is rated Medium
The name suggests merging Google Search Console (GSC) data into an audit, which implies combining/writing data rather than purely reading. However, the description is empty, so confidence is low. Given the sibling tool 'librecrawl_append_gsc_section' also implies writing/appending, this tool likely modifies audit state by merging GSC data into it.
From the tool's definition Tool name 'librecrawl_merge_gsc_data' — no description provided
Attacks that exploit this kind of access
The rule that runs librecrawl_merge_gsc_data 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_merge_gsc_data, this is the rule to start with:
librecrawl_merge_gsc_data stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_merge_gsc_data call is checked against it from then on.
Questions about librecrawl_merge_gsc_data
librecrawl_merge_gsc_data is a write tool on the Librecrawl Technical Seo Audit MCP server. It is categorised as a Write tool in the Librecrawl Technical Seo Audit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Librecrawl Technical Seo Audit MCP server in PolicyLayer and add a rule for librecrawl_merge_gsc_data: 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_merge_gsc_data is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the librecrawl_merge_gsc_data 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_merge_gsc_data. 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_merge_gsc_data 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