WordPress 태그를 삭제합니다. 태그 삭제 시 force=true가 필요합니다.
AI agents call deleteTag to permanently remove resources in WordPress MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes WordPress tags, which cannot be undone. Tag deletion affects content organization and associated post metadata permanently. While less critical than deleting posts themselves, tag deletion is still a destructive operation with meaningful blast radius if invoked unintentionally by an AI agent.
From the tool's definition Tool name 'deleteTag' combined with description stating it deletes WordPress tags ('WordPress 태그를 삭제합니다'). The requirement for 'force=true' parameter confirms irreversible deletion semantics.
Attacks that exploit this kind of access
WordPress 태그를 삭제합니다. 태그 삭제 시 force=true가 필요합니다. It is categorised as a Destructive tool in the WordPress MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for deleteTag: 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.
deleteTag is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the deleteTag 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 deleteTag. 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.
deleteTag 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 →