list_incident_roles
AI agents call list_incident_roles 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 appears to retrieve or enumerate incident roles, a read-only operation. The name structure strongly suggests it queries existing data rather than creates, modifies, or deletes. Even without a description, the naming convention and server context (Rootly incident management) support classifying this as a Read operation.
From the tool's definition Tool name 'list_incident_roles' with 'list' prefix indicates data retrieval. No description provided, but sibling tools like 'get_incident', 'get_oncall_schedule_summary' suggest this server performs incident management queries.
Documented attack patterns abuse exactly the kind of access list_incident_roles 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 list_incident_roles:
{
"version": "1",
"default": "deny",
"tools": {
"list_incident_roles": {}
}
}list_incident_roles 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.
list_incident_roles. 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 list_incident_roles: 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.
list_incident_roles 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 list_incident_roles 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 list_incident_roles. 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.
list_incident_roles 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.