Edit a WordPress file using search/replace blocks. Supports dry_run to preview diff.
AI agents use sitebay_edit_file to create or update resources in SiteBay MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SiteBay MCP Server environment.
This tool creates or modifies file data reversibly, which places it in the Write category. It is not Destructive because changes can be undone (backed by the dry_run preview capability and file version control).
From the tool's definition Tool description states 'Edit a WordPress file using search/replace blocks' and supports 'dry_run to preview diff'. The action modifies file contents reversibly through search/replace operations.
Attacks that exploit this kind of access
Edit a WordPress file using search/replace blocks. Supports dry_run to preview diff. It is categorised as a Write tool in the SiteBay MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SiteBay MCP Server MCP server in PolicyLayer and add a rule for sitebay_edit_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_edit_file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sitebay_edit_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_edit_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_edit_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 →