List the path of all webpages from sitemap.xml
AI agents call list_pages to retrieve information from Dedalus MCP Documentation Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves sitemap data and returns a list of webpage paths. It has no side effects, does not modify data, does not execute code, and does not involve financial transactions. It is a straightforward read operation querying static site metadata. The blast radius of misuse is minimal—an agent could enumerate pages but cannot interact with them or cause damage.
From the tool's definition Tool name is 'list_pages' and description states it 'List[s] the path of all webpages from sitemap.xml' — a purely informational operation that retrieves and returns metadata without modification or execution.
Attacks that exploit this kind of access
List the path of all webpages from sitemap.xml. It is categorised as a Read tool in the Dedalus MCP Documentation Server MCP Server, which means it retrieves data without modifying state.
Register the Dedalus MCP Documentation 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 Dedalus MCP Documentation 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 Dedalus MCP Documentation Server MCP server (kbhuw/dedalus-marketplace). 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 →