AI agents use close_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 'Closed'. While closing an incident is a significant operational action with potential business impact (it may affect SLA tracking, ticket visibility, or workflow processes), the action is reversible—incidents can be reopened or re-created. It does not delete data or cause permanent destruction, nor does it execute arbitrary code or move financial assets.
From the tool's definition Tool name 'close_incident' and description 'Close an incident by setting state to Closed (7)' indicate a state modification operation.
Documented attack patterns abuse exactly the kind of access close_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 close_incident:
{
"version": "1",
"default": "deny",
"tools": {
"close_incident": {
"limits": [
{
"counter": "close_incident_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}close_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.
Close an incident by setting state to Closed (7). 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 close_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.
close_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 close_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 close_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.
close_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.