List all crawled pages with optional filtering and sorting
AI agents call list_pages to retrieve information from Spider MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries already-crawled page metadata without creating, modifying, deleting, or executing operations. It presents no side effects and poses minimal security risk even if misused by an agent—the worst outcome would be listing pages the agent should not see, a data exposure concern rather than a capability to cause damage.
From the tool's definition Tool name 'list_pages' combined with description 'List all crawled pages with optional filtering and sorting' indicates data retrieval with no modification capability. The verbs 'list' and filtering/sorting operations are purely read-only actions.
Attacks that exploit this kind of access
List all crawled pages with optional filtering and sorting. It is categorised as a Read tool in the Spider MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Spider 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 Spider 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 Spider MCP Server MCP server (oeo/spider-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 →