List all documentation pages for a project, grouped by section. Returns sections with their pages (title, id, section, sortOrder). Use this to see what documentation exists before creating or updating pages. Automatically uses the linked project if no projectId is provided.
AI agents call doc_page_list to retrieve information from DevFlow MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
doc_page_list performs a read-only operation that queries and lists existing documentation metadata. It has no side effects, creates no data, executes no code, and cannot delete or modify anything. This is a straightforward informational query, warranting the Read category with low severity since it only exposes documentation structure and metadata.
From the tool's definition Tool description states 'List all documentation pages for a project' and 'Returns sections with their pages' — pure retrieval with no modification, deletion, or execution. The purpose is explicitly to 'see what documentation exists', a query operation.
Attacks that exploit this kind of access
List all documentation pages for a project, grouped by section. Returns sections with their pages (title, id, section, sortOrder). Use this to see what documentation exists before creating or updating pages. Automatically uses the linked project if no projectId is provided. It is categorised as a Read tool in the DevFlow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DevFlow MCP Server MCP server in PolicyLayer and add a rule for doc_page_list: 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 DevFlow MCP Server. Nothing to install.
doc_page_list 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 doc_page_list 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 doc_page_list. 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.
doc_page_list is provided by the DevFlow MCP Server MCP server (klausfreiberufler/devflow-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 →