Read a Shelby documentation page by exact path, title, URL, page ID, or fuzzy query.
AI agents call read_shelby_doc 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 retrieves documentation content without modifying, executing, or deleting data. It performs a simple query/fetch operation characteristic of Read category tools. The read-only nature of the server and the retrieval-focused operation present minimal security risk.
From the tool's definition Tool description states 'Read a Shelby documentation page' and server is explicitly described as 'read-only MCP server that provides searchable access to...documentation'.
Attacks that exploit this kind of access
Read a Shelby documentation page by exact path, title, URL, page ID, or fuzzy query. 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 read_shelby_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 Shelby docs MCP. Nothing to install.
read_shelby_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_shelby_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_shelby_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_shelby_doc 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 →