Reads recent Local site logs and Local app logs, including WordPress debug.log, PHP, nginx, and Local
AI agents call local_logs 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 only retrieves and displays existing log files for diagnostic purposes. It does not modify, delete, or execute any operations. Reading logs is a safe information-gathering activity with no side effects on the system state. The severity is low because log data typically contains non-sensitive diagnostic information, and viewing logs cannot cause harm to the system or data.
From the tool's definition "Reads recent Local site logs" - the verb 'reads' and the function of retrieving log files indicates data retrieval with no modification or execution. The tool accesses WordPress debug.log, PHP, nginx, and Local application logs.
Attacks that exploit this kind of access
Reads recent Local site logs and Local app logs, including WordPress debug.log, PHP, nginx, and Local. 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 local_logs: 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.
local_logs 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 local_logs 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 local_logs. 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.
local_logs 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 →