Get the structure of all available documentation files
AI agents call get_doc_structure to retrieve information from Laravel AI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about documentation organization without creating, modifying, deleting, or executing any operations. It has no side effects and presents minimal risk. The blast radius of misuse is negligible—an AI agent querying documentation structure cannot cause harm to systems or data.
From the tool's definition Tool name 'get_doc_structure' and description 'Get the structure of all available documentation files' indicate a retrieval/query operation. The verb 'Get' and the focus on structure inspection (not modification) confirm this is a read-only operation.
Attacks that exploit this kind of access
Get the structure of all available documentation files. It is categorised as a Read tool in the Laravel AI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Laravel AI MCP Server 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 Laravel AI MCP Server. 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 Laravel AI MCP Server MCP server (pujandan/mcp-laravel). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →