Verify the stored cookies can access Steady (checks /check-ins).
AI agents call steady_ping to retrieve information from Steady MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only verification/health-check by accessing the /check-ins endpoint to confirm authentication cookies are valid. It retrieves data to verify access without modifying anything.
From the tool's definition Verify the stored cookies can access Steady (checks /check-ins)
Attacks that exploit this kind of access
Verify the stored cookies can access Steady (checks /check-ins). It is categorised as a Read tool in the Steady MCP MCP Server, which means it retrieves data without modifying state.
Register the Steady MCP server in PolicyLayer and add a rule for steady_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 Steady MCP. Nothing to install.
steady_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 steady_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 steady_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.
steady_ping is provided by the Steady MCP server (sarthak-ignite/steady-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 →