Get the complete documentation directory structure with file paths and descriptions. Useful for understanding the organization of documentation.
AI agents call get_doc_structure 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 presents information about documentation structure—directory listings and metadata. It has no side effects, does not execute code, modify data, delete resources, or commit financial obligations. The maximum risk is information disclosure about documentation organization, which is low severity. It falls clearly into the Read category.
From the tool's definition Tool name 'get_doc_structure' and description 'Get the complete documentation directory structure with file paths and descriptions' indicate retrieval of structural metadata without modification.
Documented attack patterns abuse exactly the kind of access get_doc_structure 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 get_doc_structure:
{
"version": "1",
"default": "deny",
"tools": {
"get_doc_structure": {}
}
}get_doc_structure 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.
Get the complete documentation directory structure with file paths and descriptions. Useful for understanding the organization of documentation. 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 get_doc_structure: 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.
get_doc_structure 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 get_doc_structure 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 get_doc_structure. 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.
get_doc_structure 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.