List documentation pages, optionally filtered by slug prefix.
AI agents call list_pages to retrieve information from Reflex Docs MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only lists/enumerates documentation pages, similar to other Read-category tools on the server (get_doc, list_components, list_recipes, get_code_examples). It has no capability to modify, delete, execute, or financially impact any system. The blast radius of misuse is minimal—an agent could retrieve information about available pages but cannot cause harm.
From the tool's definition Tool description states it 'List documentation pages, optionally filtered by slug prefix' — a pure retrieval operation with no data modification, execution, or side effects.
Attacks that exploit this kind of access
List documentation pages, optionally filtered by slug prefix. It is categorised as a Read tool in the Reflex Docs MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Reflex Docs MCP Server MCP server in PolicyLayer and add a rule for list_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 Reflex Docs MCP Server. Nothing to install.
list_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_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_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_pages is provided by the Reflex Docs MCP Server MCP server (itsmeadarsh2008/reflex-docs-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 →