Check for broken links and redirects on web pages
AI agents call check_broken_links to retrieve information from MCP Web Scrape without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes link status information from web pages—a read-only operation with no side effects. It returns diagnostic data about link health without creating, modifying, deleting, or executing any actions on target systems. The blast radius of misuse is minimal, as the worst outcome would be generation of false or misleading reports about link status.
From the tool's definition Tool name 'check_broken_links' and description 'Check for broken links and redirects on web pages' indicate a purely informational operation that identifies broken links and redirect chains without modifying any content.
Documented attack patterns abuse exactly the kind of access check_broken_links gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Web Scrape, and nothing reaches the server without passing your rules. This is the rule we recommend for check_broken_links:
{
"version": "1",
"default": "deny",
"tools": {
"check_broken_links": {}
}
}check_broken_links is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check for broken links and redirects on web pages. It is categorised as a Read tool in the MCP Web Scrape MCP Server, which means it retrieves data without modifying state.
Register the MCP Web Scrape MCP server in PolicyLayer and add a rule for check_broken_links: 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 MCP Web Scrape. Nothing to install.
check_broken_links 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 check_broken_links 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 check_broken_links. 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.
check_broken_links is provided by the MCP Web Scrape MCP server (mukul975/mcp-web-scrape). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Web Scrape, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
48 MCP Web Scrape tools catalogued and risk-classified — across an index of 43,000+ MCP servers.