Read a specific Shelby documentation page by its exact chunk ID.
AI agents call get_shelby_doc_chunk to retrieve information from Shelby docs MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a straightforward data retrieval operation on static documentation. It has no side effects, cannot modify or delete data, and cannot execute code or commands. The read-only nature of the server and the retrieval-only function of this tool place it firmly in the Read category with low severity.
From the tool's definition Tool description states 'Read a specific Shelby documentation page' and server is explicitly described as 'read-only MCP server'. The tool retrieves documentation content by chunk ID with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Read a specific Shelby documentation page by its exact chunk ID. It is categorised as a Read tool in the Shelby docs MCP MCP Server, which means it retrieves data without modifying state.
Register the Shelby docs MCP server in PolicyLayer and add a rule for get_shelby_doc_chunk: 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 Shelby docs MCP. Nothing to install.
get_shelby_doc_chunk 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_shelby_doc_chunk 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_shelby_doc_chunk. 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_shelby_doc_chunk is provided by the Shelby docs MCP server (jr-kenny/shelby-mcp). 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 →