check_responder_availability
AI agents call check_responder_availability to retrieve information from Rootly without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name strongly implies a status check or availability query operation typical of incident management systems. Based on naming patterns and sibling tools that are predominantly read operations (get_*, check_*, collect_*), this appears to be a data retrieval function with no side effects.
From the tool's definition Tool name 'check_responder_availability' suggests querying availability status. Sibling tools include read operations like 'get_alert_by_short_id', 'get_incident', 'get_oncall_schedule_summary', and 'get_oncall_shift_metrics', indicating this server primarily…
Documented attack patterns abuse exactly the kind of access check_responder_availability gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Rootly, and nothing reaches the server without passing your rules. This is the rule we recommend for check_responder_availability:
{
"version": "1",
"default": "deny",
"tools": {
"check_responder_availability": {}
}
}check_responder_availability is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
check_responder_availability. It is categorised as a Read tool in the Rootly MCP Server, which means it retrieves data without modifying state.
Register the Rootly MCP server in PolicyLayer and add a rule for check_responder_availability: 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 Rootly. Nothing to install.
check_responder_availability 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 check_responder_availability 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 check_responder_availability. 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.
check_responder_availability is provided by the Rootly MCP server (https://mcp.rootly.com/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Rootly, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 Rootly tools catalogued and risk-classified — across an index of 43,000+ MCP servers.