Scan posts for all shortcodes in use and return a report. Helps identify which shortcodes need configuration before export.
AI agents call shortcode_scan to retrieve information from WP Astro MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only analysis of existing WordPress content to identify shortcodes. It queries data, aggregates findings, and returns information without modifying posts, executing code, or creating side effects. The scanning operation supports the migration workflow by auditing content before export, which is purely informational.
From the tool's definition Tool description states it 'Scan posts for all shortcodes in use and return a report.' The verb 'scan' and 'report' indicate data retrieval and analysis only. No modification, deletion, execution, or financial operations are described.
Documented attack patterns abuse exactly the kind of access shortcode_scan 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_scan:
{
"version": "1",
"default": "deny",
"tools": {
"shortcode_scan": {}
}
}shortcode_scan is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Scan posts for all shortcodes in use and return a report. Helps identify which shortcodes need configuration before export. It is categorised as a Read tool in the WP Astro MCP MCP Server, which means it retrieves data without modifying state.
Register the WP Astro MCP server in PolicyLayer and add a rule for shortcode_scan: 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_scan 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 shortcode_scan 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_scan. 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_scan 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.