This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/wordpress-list-pages.md
What wordpress_list_pages does on UnClick
AI agents call wordpress_list_pages to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Pages to return (max 100, default 10) |
search | string | — | Search term |
site_url | string | Yes | WordPress site URL |
username | string | Yes | WordPress username |
app_password | string | Yes | WordPress application password |
Parameters from the server's own tool schema.
Why wordpress_list_pages is rated Low
This tool performs a query/list operation to retrieve WordPress pages without side effects. It is a straightforward read operation with minimal security risk, as it only retrieves existing page metadata. The severity is low because listing pages does not affect system state or expose sensitive information beyond what a WordPress user with read permissions would normally access.
From the tool's definition Tool name 'wordpress_list_pages' and description 'List WordPress pages' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
The rule that runs wordpress_list_pages safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wordpress_list_pages, this is the rule to start with:
wordpress_list_pages is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every wordpress_list_pages call is checked against it from then on.
Questions about wordpress_list_pages
List WordPress pages. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
wordpress_list_pages accepts 5 parameters: limit, search, site_url, username, app_password. Required: site_url, username, app_password. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for wordpress_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 UnClick. Nothing to install.
wordpress_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 wordpress_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 wordpress_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.
wordpress_list_pages is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue