Get the SSH/SFTP status for an environment.
AI agents call kinsta.environments.ssh.status 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 queries the current SSH/SFTP configuration status of an environment. It performs a read-only check without creating, modifying, deleting, or executing anything. The blast radius is minimal — an AI agent learning the SSH status of an environment poses no direct risk, though the information could inform subsequent privileged actions.
From the tool's definition Tool name includes 'status' and description states 'Get the SSH/SFTP status' — a pure retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get the SSH/SFTP status for 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.ssh.status: 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.ssh.status 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.ssh.status 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.ssh.status. 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.ssh.status 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 →