List WordPress pages with ID, title, slug and status.
AI agents call wp_list_pages to retrieve information from Mcp Wordpress without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that retrieves and lists existing WordPress page information. It has no side effects, does not modify data, and does not execute code or trigger external operations. The blast radius of misuse is minimal—an AI agent could only retrieve page information already accessible to the authenticated user. This is a straightforward data retrieval operation.
From the tool's definition Tool name 'wp_list_pages' and description 'List WordPress pages with ID, title, slug and status' indicates retrieval of page metadata without modification. Core operation is querying/listing data.
Attacks that exploit this kind of access
List WordPress pages with ID, title, slug and status. It is categorised as a Read tool in the Mcp Wordpress MCP Server, which means it retrieves data without modifying state.
Register the Mcp Wordpress MCP server in PolicyLayer and add a rule for wp_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 Mcp Wordpress. Nothing to install.
wp_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 wp_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 wp_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.
wp_list_pages is provided by the Mcp Wordpress MCP server (leonardobora/mcp-wordpress). 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 →