AI agents use update_incident to create or update resources in Rootly — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rootly environment.
The tool name 'update_incident' clearly performs a write operation on incident data. This is reversible and does not delete or destroy data (not Destructive), does not execute arbitrary code (not Execute), and does not involve financial transactions (not Financial). It modifies incident records which could affect incident tracking and response workflows.
From the tool's definition Tool name 'update_incident' indicates modification of incident data. Sibling tools include 'create_incident' and 'get_incident', establishing this as part of incident management.
Documented attack patterns abuse exactly the kind of access update_incident 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 update_incident:
{
"version": "1",
"default": "deny",
"tools": {
"update_incident": {
"limits": [
{
"counter": "update_incident_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_incident stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
update_incident. It is categorised as a Write tool in the Rootly MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rootly MCP server in PolicyLayer and add a rule for update_incident: 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.
update_incident is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_incident 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 update_incident. 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.
update_incident 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.