Comprehensive link checking for documentation deployment with external, internal, and anchor link validation
AI agents call check_documentation_links to retrieve information from Documcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs link validation—traversing and analyzing URLs and anchors in documentation to identify broken or invalid links. It retrieves and validates information about links but does not create, modify, delete, or execute any code. It has no side effects on the documentation, repository, or deployment systems.
From the tool's definition Tool name 'check_documentation_links' and description 'Comprehensive link checking for documentation deployment with external, internal, and anchor link validation' indicate validation and inspection activities.
Documented attack patterns abuse exactly the kind of access check_documentation_links gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Documcp, and nothing reaches the server without passing your rules. This is the rule we recommend for check_documentation_links:
{
"version": "1",
"default": "deny",
"tools": {
"check_documentation_links": {}
}
}check_documentation_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.
Comprehensive link checking for documentation deployment with external, internal, and anchor link validation. It is categorised as a Read tool in the Documcp MCP Server, which means it retrieves data without modifying state.
Register the Docu MCP server in PolicyLayer and add a rule for check_documentation_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 Documcp. Nothing to install.
check_documentation_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_documentation_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_documentation_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_documentation_links is provided by the Docu MCP server (tosin2013/documcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Documcp, 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.
52 Documcp tools catalogued and risk-classified — across an index of 43,000+ MCP servers.