Reads a text file inside the selected LocalWP site. The path must stay inside that site
AI agents call read_site_file 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 retrieves file content from within a LocalWP site boundary without creating, modifying, or deleting data. It has no side effects and poses minimal risk unless sensitive credentials are exposed in readable files, which is a deployment/configuration issue rather than a tool capability issue. Classified as Read with low severity due to confined scope and read-only semantics.
From the tool's definition Tool name 'read_site_file' and description 'Reads a text file' explicitly indicate data retrieval with no modification. The constraint 'path must stay inside that site' prevents directory traversal attacks but confirms the read-only nature.
Attacks that exploit this kind of access
Reads a text file inside the selected LocalWP site. The path must stay inside that site. 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 read_site_file: 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.
read_site_file 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 read_site_file 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 read_site_file. 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.
read_site_file 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 →