check_urls

Check HTTP status codes for a list of URLs. Returns status code, redirect destination (if redirected), and response time for each URL. Use this to: - Verify expired job pages are handled correctly - Check for broken links - Analyze redirect chains

Server SEO Audit MCP Server richarddillman/seo-audit-mcp
Category Read
Risk class Low
Parameters 00 required

What check_urls does on SEO Audit MCP Server

AI agents call check_urls to retrieve information from SEO Audit MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why check_urls needs a policy

check_urls retrieves HTTP metadata about URLs without side effects. It queries web servers for response information but does not create, modify, delete, or execute operations. This is purely informational/diagnostic in nature, making it a Read category tool with low severity since misuse would only gather network information without operational impact.

From the tool's definition Tool performs HTTP status checking and returns 'status code, redirect destination, and response time' — these are read-only queries with no data modification, deletion, or code execution.

Questions about check_urls

What does the check_urls tool do? +

Check HTTP status codes for a list of URLs. Returns status code, redirect destination (if redirected), and response time for each URL. Use this to: - Verify expired job pages are handled correctly - Check for broken links - Analyze redirect chains. It is categorised as a Read tool in the SEO Audit MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_urls? +

Register the SEO Audit MCP Server MCP server in PolicyLayer and add a rule for check_urls: 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 SEO Audit MCP Server. Nothing to install.

What risk level is check_urls? +

check_urls is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_urls? +

Yes. Add a rate_limit block to the check_urls 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.

How do I block check_urls completely? +

Set action: deny in the PolicyLayer policy for check_urls. 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.

What MCP server provides check_urls? +

check_urls is provided by the SEO Audit MCP Server MCP server (richarddillman/seo-audit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.