List available Shelby documentation pages, optionally filtered by path or title text.
AI agents call list_shelby_doc_pages 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 is a pure read operation that retrieves and displays documentation metadata. The filtering is applied to existing documentation without any side effects. Blast radius is minimal—at worst, an AI agent learns what documentation exists, which poses no security risk.
From the tool's definition Tool name 'list_shelby_doc_pages' and description explicitly state it 'lists available Shelby documentation pages'. Server description confirms 'read-only MCP server' with 'search, list, and read' capabilities.
Attacks that exploit this kind of access
List available Shelby documentation pages, optionally filtered by path or title text. 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 list_shelby_doc_pages: 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.
list_shelby_doc_pages 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 list_shelby_doc_pages 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 list_shelby_doc_pages. 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.
list_shelby_doc_pages 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 →