List all available documentation files organized by category. Use this to discover what documentation is available or to get an overview of the documentation structure.
AI agents call list_docs to retrieve information from Project MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists existing documentation; it has no side effects, does not create, modify, delete, or execute any operations. It is a straightforward discovery/enumeration function that falls clearly into the Read category with low severity since listing documentation poses minimal security risk even if misused.
From the tool's definition Tool name and description indicate it 'List all available documentation files' and 'discover what documentation is available' — these are read-only operations that query and retrieve information without modifying state.
Documented attack patterns abuse exactly the kind of access list_docs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Project MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for list_docs:
{
"version": "1",
"default": "deny",
"tools": {
"list_docs": {}
}
}list_docs 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.
List all available documentation files organized by category. Use this to discover what documentation is available or to get an overview of the documentation structure. It is categorised as a Read tool in the Project MCP MCP Server, which means it retrieves data without modifying state.
Register the Project MCP server in PolicyLayer and add a rule for list_docs: 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 Project MCP. Nothing to install.
list_docs 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 list_docs 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 list_docs. 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.
list_docs is provided by the Project MCP server (pouyanafisi/project-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Project MCP, 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.
42 Project MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.