Resolves one LocalWP site and returns its WordPress, PHP, and MySQL runtime details.
AI agents call local_site_info to retrieve information from LocalWP MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves runtime environment information about a LocalWP site. It performs introspection only—gathering diagnostic data about WordPress, PHP, and MySQL versions/configuration—without creating, modifying, executing, or deleting anything.
From the tool's definition Tool description states it 'Resolves one LocalWP site and returns its WordPress, PHP, and MySQL runtime details.' The verb 'returns' indicates data retrieval with no modification or execution. No side effects are described.
Attacks that exploit this kind of access
Resolves one LocalWP site and returns its WordPress, PHP, and MySQL runtime details. It is categorised as a Read tool in the LocalWP MCP MCP Server, which means it retrieves data without modifying state.
Register the LocalWP MCP server in PolicyLayer and add a rule for local_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 LocalWP MCP. Nothing to install.
local_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 local_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 local_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.
local_site_info is provided by the LocalWP MCP server (kazimshah39/localwp-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 →