Verify that Screaming Frog SEO Spider is installed and the CLI is accessible.
AI agents call sf_check to retrieve information from Screaming Frog SEO Spider MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries the system state to determine if a prerequisite dependency is installed and accessible. It retrieves status information without creating, modifying, deleting, or executing any operations. This is a diagnostic read operation with minimal blast radius if misused.
From the tool's definition The tool 'sf_check' is described as 'Verify that Screaming Frog SEO Spider is installed and the CLI is accessible' — it performs a check/verification operation with no side effects, no data modification, and no external state changes.
Attacks that exploit this kind of access
Verify that Screaming Frog SEO Spider is installed and the CLI is accessible. It is categorised as a Read tool in the Screaming Frog SEO Spider MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Screaming Frog SEO Spider MCP Server MCP server in PolicyLayer and add a rule for sf_check: 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 Screaming Frog SEO Spider MCP Server. Nothing to install.
sf_check 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 sf_check 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 sf_check. 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.
sf_check is provided by the Screaming Frog SEO Spider MCP Server MCP server (pypi:screaming-frog-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →