Deep analysis of a WordPress site: count all content types, detect plugins, audit shortcodes, check media, and generate readiness report.
AI agents call site_analyze 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.
site_analyze is a reconnaissance and assessment tool that queries WordPress site data through REST API to generate a readiness report. It retrieves and analyzes existing data without modifying content, executing code, or triggering external operations. The analysis phase of a migration is a read-only operation—examining what exists to inform subsequent decisions.
From the tool's definition Tool performs deep analysis and auditing operations: 'count all content types, detect plugins, audit shortcodes, check media, and generate readiness report.' All verbs indicate information gathering and reporting with no modifications, deletions, or code…
Documented attack patterns abuse exactly the kind of access site_analyze 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 site_analyze:
{
"version": "1",
"default": "deny",
"tools": {
"site_analyze": {}
}
}site_analyze 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.
Deep analysis of a WordPress site: count all content types, detect plugins, audit shortcodes, check media, and generate readiness report. 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 site_analyze: 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.
site_analyze 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 site_analyze 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 site_analyze. 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.
site_analyze 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.