WordPress에 새 게시글을 생성합니다.
AI agents use createPost to create or update resources in WordPress MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WordPress MCP Server environment.
This tool creates new content in WordPress, which is a write operation that modifies the system state. It is not destructive (posts can be deleted), not financial, and not a read-only query. The severity is medium because uncontrolled post creation could spam a WordPress site or create unwanted content, but the impact is limited to content and reversible.
From the tool's definition Tool name 'createPost' and description 'WordPress에 새 게시글을 생성합니다' (creates a new post in WordPress) indicate content creation. This is a reversible write operation—posts can be updated or deleted afterward.
Attacks that exploit this kind of access
WordPress에 새 게시글을 생성합니다. It is categorised as a Write tool in the WordPress MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for createPost: 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.
createPost is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the createPost 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 createPost. 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.
createPost 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 →