List files in an environment
AI agents call kinsta.environments.files 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 performs a directory listing or file enumeration operation, which is non-destructive, non-modifying, and has no side effects. While it may expose information about the environment's file structure, it is fundamentally a query operation. Severity is low because file listing alone poses minimal risk unless the environment contains highly sensitive data, but the tool itself performs no harmful actions.
From the tool's definition Tool name and description explicitly state 'List files in an environment' — a read-only operation that retrieves file information without modification, deletion, or code execution.
Attacks that exploit this kind of access
List files in an environment. 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.environments.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 Kinsta MCP Server. Nothing to install.
kinsta.environments.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 kinsta.environments.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 kinsta.environments.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.
kinsta.environments.files 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 →