Searches text files inside the selected LocalWP site for a literal string match.
AI agents call search_site_files 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 and queries file content without any side effects. It performs a search operation analogous to grep or file search utilities, which is a classic Read category activity. The literal string matching constraint further limits any potential for abuse. Low severity because the blast radius is confined to information disclosure of file contents already accessible within the LocalWP environment.
From the tool's definition Tool description states it "Searches text files inside the selected LocalWP site for a literal string match" — a pure query operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Searches text files inside the selected LocalWP site for a literal string match. 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 search_site_files: 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.
search_site_files 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 search_site_files 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 search_site_files. 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.
search_site_files 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 →