AI agents call list-posts to retrieve information from AutoWP MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves post data from WordPress with filtering and pagination capabilities. It performs no write, delete, execute, or financial operations. The blast radius of misuse is minimal—an attacker could enumerate posts but cannot modify, delete, or publish content, nor execute code or access sensitive user data through listing alone. This is a straightforward read operation.
From the tool's definition Tool name 'list-posts' and description 'List WordPress posts with pagination and filters' indicate data retrieval only. The verb 'list' is a read operation with no modification, deletion, or side effects.
Documented attack patterns abuse exactly the kind of access list-posts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AutoWP MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list-posts:
{
"version": "1",
"default": "deny",
"tools": {
"list-posts": {}
}
}list-posts is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List WordPress posts with pagination and filters. It is categorised as a Read tool in the AutoWP MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AutoWP MCP Server MCP server in PolicyLayer and add a rule for list-posts: 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 AutoWP MCP Server. Nothing to install.
list-posts 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-posts 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-posts. 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-posts is provided by the AutoWP MCP Server MCP server (njengah/autowpmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AutoWP MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
47 AutoWP MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.