Read a text file inside a Studio site directory. Safe: only allows files within the given sitePath. Has a size limit.
AI agents call wpdev_fs_read_file to retrieve information from WordPress Developer 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 file contents with built-in restrictions (directory sandboxing and size limits) and produces no side effects. It is a straightforward read operation with minimal blast radius—a misused instance could leak sensitive configuration or credentials stored in text files, but cannot modify or delete data. Severity is low because the attack surface is constrained by the documented safety guardrails.
From the tool's definition Tool name includes 'read' and description states 'Read a text file inside a Studio site directory.' The description explicitly notes 'Safe: only allows files within the given sitePath' with a size limit, confirming read-only semantics with access controls.
Documented attack patterns abuse exactly the kind of access wpdev_fs_read_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WordPress Developer MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for wpdev_fs_read_file:
{
"version": "1",
"default": "deny",
"tools": {
"wpdev_fs_read_file": {}
}
}wpdev_fs_read_file 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.
Read a text file inside a Studio site directory. Safe: only allows files within the given sitePath. Has a size limit. It is categorised as a Read tool in the WordPress Developer MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WordPress Developer MCP Server MCP server in PolicyLayer and add a rule for wpdev_fs_read_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 WordPress Developer MCP Server. Nothing to install.
wpdev_fs_read_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 wpdev_fs_read_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 wpdev_fs_read_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.
wpdev_fs_read_file is provided by the WordPress Developer MCP Server MCP server (nightnei/wordpress-developer-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 25 WordPress Developer MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
25 WordPress Developer MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.