Get log file contents for an environment. Supports error.log and access.log.
AI agents call kinsta.logs.get to retrieve information from Kinsta 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 and queries existing log files (error.log and access.log) without modifying, deleting, or executing any operations. It has no capability to change state or trigger external actions. The blast radius of misuse is minimal—worst case being exposure of log data that may contain sensitive information, but no destructive or operational damage. This is a straightforward Read operation.
From the tool's definition Tool description states 'Get log file contents for an environment. Supports error.log and access.log.' The verb 'Get' and explicit reference to retrieving log file contents indicates data retrieval with no side effects.
Attacks that exploit this kind of access
Get log file contents for an environment. Supports error.log and access.log. It is categorised as a Read tool in the Kinsta MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kinsta MCP Server MCP server in PolicyLayer and add a rule for kinsta.logs.get: 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 Kinsta MCP Server. Nothing to install.
kinsta.logs.get 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 kinsta.logs.get 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 kinsta.logs.get. 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.
kinsta.logs.get is provided by the Kinsta MCP Server MCP server (jacob-hartmann/kinsta-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 →