WordPress 게시글 목록을 조회합니다. 페이지네이션, 검색, 상태 필터를 지원합니다.
AI agents call listPosts to retrieve information from WordPress 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 WordPress posts with filtering and pagination capabilities—a non-destructive query operation with no side effects. It fits the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' Severity is low because misuse by an AI agent would only expose or reveal existing post data, with no ability to modify, delete, or execute operations.
From the tool's definition Tool name 'listPosts' and description indicating it 'retrieves/queries' a list of posts with pagination, search, and status filtering. No data modification, deletion, or external code execution occurs.
Attacks that exploit this kind of access
WordPress 게시글 목록을 조회합니다. 페이지네이션, 검색, 상태 필터를 지원합니다. It is categorised as a Read tool in the WordPress MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for listPosts: 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 WordPress MCP Server. Nothing to install.
listPosts 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 listPosts 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 listPosts. 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.
listPosts is provided by the WordPress MCP Server MCP server (ssong-openmaru-io/ai-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 →