Get WordPress site information and capabilities
AI agents call get_site_info to retrieve information from WordPress MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves WordPress site metadata and configuration information without performing any side effects. It is a read-only operation that queries site data, matching the 'Read' category pattern (get, fetch, retrieve). The low severity reflects minimal blast radius—an AI agent misusing this tool could only learn about site structure and capabilities, not cause harm or data loss.
From the tool's definition Tool name 'get_site_info' and description 'Get WordPress site information and capabilities' indicate data retrieval with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get WordPress site information and capabilities. It is categorised as a Read tool in the WordPress MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for get_site_info: 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 WordPress MCP Server. Nothing to install.
get_site_info 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 get_site_info 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 get_site_info. 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.
get_site_info is provided by the WordPress MCP Server MCP server (wolffcatskyy/wordpress-mcp). 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 →