Read a specific documentation file
AI agents call read_doc 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 and queries static documentation files with no side effects, no code execution capability, and no data modification. It falls squarely into the Read category. Severity is low because documentation access poses minimal risk even if misused by an AI agent—the worst outcome would be accessing or disclosing documentation that may already be public or intended for internal reference.
From the tool's definition Tool name 'read_doc' and description 'Read a specific documentation file' clearly indicate retrieval of documentation content without modification or execution.
Attacks that exploit this kind of access
Read a specific documentation file. 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 read_doc: 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.
read_doc 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 read_doc 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 read_doc. 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.
read_doc 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 →