Insert a new shortcode into a page, positioned before or after an existing shortcode.
AI agents use wp_insert_shortcode to create or update resources in Mcp Wordpress — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Wordpress environment.
This tool creates new content (a shortcode) within a WordPress page, modifying the page structure reversibly. It is not destructive (no deletion), not financial, and not execute-level (it doesn't run arbitrary code—it inserts a pre-defined shortcode).
From the tool's definition Tool name 'wp_insert_shortcode' and description states it will 'Insert a new shortcode into a page', which is a create/modify action. The server description confirms it 'edit[s]' WordPress content via REST API.
Attacks that exploit this kind of access
Insert a new shortcode into a page, positioned before or after an existing shortcode. It is categorised as a Write tool in the Mcp Wordpress MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Wordpress MCP server in PolicyLayer and add a rule for wp_insert_shortcode: 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 Mcp Wordpress. Nothing to install.
wp_insert_shortcode 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 wp_insert_shortcode 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 wp_insert_shortcode. 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.
wp_insert_shortcode is provided by the Mcp Wordpress MCP server (leonardobora/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 →