Lists files and directories inside the selected LocalWP site. Paths are scoped to that site
AI agents call list_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 information about site files without creating, modifying, deleting, or executing any code. It is a straightforward read operation analogous to 'ls' or 'list'. Severity is low because directory enumeration has limited blast radius—an attacker gains filesystem visibility but cannot alter data or execute actions. The scope limitation to a single site further reduces risk.
From the tool's definition Tool name 'list_site_files' and description 'Lists files and directories inside the selected LocalWP site' indicate a query/enumeration operation with no modifications or side effects. Scoping to the site boundary further confirms containment.
Attacks that exploit this kind of access
Lists files and directories inside the selected LocalWP site. Paths are scoped to 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 list_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.
list_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 list_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 list_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.
list_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 →