AI agents call seo_check to retrieve information from Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | URL to check |
Parameters from the server's own tool schema.
The tool retrieves and analyzes SEO metrics for a given URL, providing informational output only. It has no ability to modify data, execute commands, delete information, or create financial obligations. The operation is read-only with no side effects beyond returning analysis results.
From the tool's definition Tool performs a 'Quick SEO health check' and 'Returns score and issues list' - these are query/analysis operations with no data modification, deletion, or code execution capabilities.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
Quick SEO health check for any URL. Returns score and issues list. It is categorised as a Read tool in the Tools MCP Server, which means it retrieves data without modifying state.
seo_check accepts 1 parameter: url. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the Tools MCP server in PolicyLayer and add a rule for seo_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 Tools. Nothing to install.
seo_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 seo_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 seo_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.
seo_check is provided by the Tools MCP server (https://www.jiebang.site/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 →