List available actions, optionally filtered by category.
AI agents call wp_astro_help 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 is a help/documentation tool that queries and returns information about available actions. It has no side effects, does not create, modify, or delete data, and does not execute external operations. It is purely informational and belongs in the Read category with low severity due to its benign nature.
From the tool's definition Tool name 'wp_astro_help' and description 'List available actions, optionally filtered by category' indicate a read-only operation that retrieves and displays information about available commands without modifying any data.
Documented attack patterns abuse exactly the kind of access wp_astro_help 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 wp_astro_help:
{
"version": "1",
"default": "deny",
"tools": {
"wp_astro_help": {}
}
}wp_astro_help 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.
List available actions, optionally filtered by category. 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 wp_astro_help: 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.
wp_astro_help 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 wp_astro_help 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_astro_help. 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_astro_help 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.