Configure how a specific shortcode should be handled during conversion. Actions: strip (remove entirely), keep_content (unwrap), remove (delete including content), component (map to Astro component), html (convert to HTML).
AI agents use shortcode_configure to create or update resources in WP Astro MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WP Astro MCP environment.
This tool modifies conversion settings and can alter or delete content during the migration process. While it doesn't permanently destroy source data (the original WordPress site remains unchanged), it creates modified output that overwrites previous conversion decisions.
From the tool's definition The tool description explicitly states it "Configure[s] how a specific shortcode should be handled during conversion" with actions including 'strip', 'keep_content', 'remove', 'component', and 'html'.
Documented attack patterns abuse exactly the kind of access shortcode_configure gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WP Astro MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for shortcode_configure:
{
"version": "1",
"default": "deny",
"tools": {
"shortcode_configure": {
"limits": [
{
"counter": "shortcode_configure_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}shortcode_configure stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Configure how a specific shortcode should be handled during conversion. Actions: strip (remove entirely), keep_content (unwrap), remove (delete including content), component (map to Astro component), html (convert to HTML). It is categorised as a Write tool in the WP Astro MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WP Astro MCP server in PolicyLayer and add a rule for shortcode_configure: 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 WP Astro MCP. Nothing to install.
shortcode_configure 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 shortcode_configure 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 shortcode_configure. 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.
shortcode_configure is provided by the WP Astro MCP server (vapvarun/wp-astro-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WP Astro MCP, 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.
60 WP Astro MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.