Check that the Kinsta MCP server is running and that API credentials
AI agents call kinsta.ping 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.
A ping/health-check tool verifies connectivity and credential validity by querying status, producing no modifications, deletions, or external side effects. It is purely informational and therefore classified as Read with low severity.
From the tool's definition Tool is named 'kinsta.ping' and description indicates it 'Check[s] that the Kinsta MCP server is running and that API credentials' — this is a health check that only retrieves status information with no side effects.
Attacks that exploit this kind of access
Check that the Kinsta MCP server is running and that API credentials. 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.ping: 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.ping 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.ping 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.ping. 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.ping 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 →