Scan documentation directory for staleness markers and identify files needing updates based on configurable time thresholds (minutes, hours, days)
AI agents call track_documentation_freshness 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 inspection and analysis of documentation state by reading timestamps and metadata. It produces reports on staleness but does not execute deployments, modify files, delete content, or trigger external operations. The configurable time thresholds control the reporting criteria, not destructive or write actions.
From the tool's definition The tool 'scan[s] documentation directory for staleness markers and identify[s] files needing updates' — it retrieves and analyzes metadata without modifying or deleting data. The verbs 'scan' and 'identify' indicate passive inspection.
Documented attack patterns abuse exactly the kind of access track_documentation_freshness 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 track_documentation_freshness:
{
"version": "1",
"default": "deny",
"tools": {
"track_documentation_freshness": {}
}
}track_documentation_freshness 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.
Scan documentation directory for staleness markers and identify files needing updates based on configurable time thresholds (minutes, hours, days). 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 track_documentation_freshness: 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.
track_documentation_freshness 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 track_documentation_freshness 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 track_documentation_freshness. 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.
track_documentation_freshness 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.