Read a WordPress file from wp-content/. Supports line ranges.
AI agents call sitebay_read_file to retrieve information from SiteBay 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 from a constrained directory (wp-content/) without side effects. It is a straightforward read operation that queries existing data. The scope is limited to WordPress content files, reducing blast radius. Even if an AI agent misuses it by reading sensitive configuration files, the damage is limited to information disclosure rather than data modification or destruction.
From the tool's definition Tool name is 'sitebay_read_file' and description states 'Read a WordPress file from wp-content/'. The verb 'Read' and the operation described ('read a file') indicate data retrieval with no modification or deletion.
Attacks that exploit this kind of access
Read a WordPress file from wp-content/. Supports line ranges. It is categorised as a Read tool in the SiteBay MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SiteBay MCP Server MCP server in PolicyLayer and add a rule for sitebay_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 SiteBay MCP Server. Nothing to install.
sitebay_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 sitebay_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 sitebay_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.
sitebay_read_file is provided by the SiteBay MCP Server MCP server (sitebay/sitebay-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 →