check_sitemap

Fetch a sitemap.xml file and check all listed URLs for broken links, redirects, and timeouts. Supports sitemap index files.

Server Deadlink Checker yifanyifan897645/deadlink-checker-mcp
Category Read
Risk class Low
Parameters 00 required

What check_sitemap does on Deadlink Checker

AI agents call check_sitemap to retrieve information from Deadlink Checker without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why check_sitemap needs a policy

This tool retrieves sitemap data and checks link status (read-only HTTP HEAD/GET requests). It performs no mutations, executions, deletions, or financial transactions. The severity is low because even if misused by an agent, it merely queries external resources and reports their status with no side effects or blast radius to systems or data.

From the tool's definition Tool 'check_sitemap' performs URL validation operations: 'Fetch a sitemap.xml file and check all listed URLs for broken links, redirects, and timeouts.' These are diagnostic read operations that retrieve and analyze data without modifying, deleting, or…

Questions about check_sitemap

What does the check_sitemap tool do? +

Fetch a sitemap.xml file and check all listed URLs for broken links, redirects, and timeouts. Supports sitemap index files. It is categorised as a Read tool in the Deadlink Checker MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_sitemap? +

Register the Deadlink Checker MCP server in PolicyLayer and add a rule for check_sitemap: 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 Deadlink Checker. Nothing to install.

What risk level is check_sitemap? +

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

Can I rate-limit check_sitemap? +

Yes. Add a rate_limit block to the check_sitemap 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_sitemap completely? +

Set action: deny in the PolicyLayer policy for check_sitemap. 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_sitemap? +

check_sitemap is provided by the Deadlink Checker MCP server (yifanyifan897645/deadlink-checker-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.