Resolve an incident by setting state to Resolved (6) with resolution notes.
AI agents use resolve_incident to create or update resources in Now Sdk Ext — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Now Sdk Ext environment.
This tool modifies incident data by changing its state to a terminal status (Resolved) and adding resolution notes. While it does not delete data or move money, it irreversibly changes incident state in a way that affects workflow—once resolved, an incident's status is marked as complete.
From the tool's definition The tool description explicitly states it 'Resolve[s] an incident by setting state to Resolved (6) with resolution notes,' which modifies the state field of an incident record.
Documented attack patterns abuse exactly the kind of access resolve_incident gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Now Sdk Ext, and nothing reaches the server without passing your rules. This is the rule we recommend for resolve_incident:
{
"version": "1",
"default": "deny",
"tools": {
"resolve_incident": {
"limits": [
{
"counter": "resolve_incident_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}resolve_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.
Resolve an incident by setting state to Resolved (6) with resolution notes. It is categorised as a Write tool in the Now Sdk Ext MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Now Sdk Ext MCP server in PolicyLayer and add a rule for resolve_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 Now Sdk Ext. Nothing to install.
resolve_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 resolve_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 resolve_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.
resolve_incident is provided by the Now Sdk Ext MCP server (sonisoft-cnanda/now-sdk-ext-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Now Sdk Ext, 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.
86 Now Sdk Ext tools catalogued and risk-classified — across an index of 43,000+ MCP servers.