Evaluate README files for community health, accessibility, and onboarding effectiveness
AI agents call evaluate_readme_health 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 assessment and analysis of README content to gather metrics about documentation quality. It retrieves and examines data from README files but does not create, modify, delete, or execute operations. No side effects are implied. This is a classic Read category tool—it queries and analyzes existing documentation.
From the tool's definition Tool description states it 'Evaluate[s] README files' for analysis of community health, accessibility, and onboarding effectiveness.
Documented attack patterns abuse exactly the kind of access evaluate_readme_health 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 evaluate_readme_health:
{
"version": "1",
"default": "deny",
"tools": {
"evaluate_readme_health": {}
}
}evaluate_readme_health 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.
Evaluate README files for community health, accessibility, and onboarding effectiveness. 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 evaluate_readme_health: 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.
evaluate_readme_health 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 evaluate_readme_health 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 evaluate_readme_health. 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.
evaluate_readme_health 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.