AI agents use natural_language_update to create or update resources in ServiceNow MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceNow MCP Server environment.
The tool name and context clearly indicate it modifies ServiceNow records via natural language input. This is a Write operation (reversible modification), but severity is high due to: (1) natural language input reducing validation/safety, (2) potential for unintended updates affecting business-critical IT service records, (3) no constraints visible on scope/target of updates.
From the tool's definition Tool name 'natural_language_update' combined with server description stating it allows users to 'update them [records]' and 'manipulate ServiceNow data'. Sibling tools include 'update_incident' and 'update_script', confirming update capability on this server.
Documented attack patterns abuse exactly the kind of access natural_language_update gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ServiceNow MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for natural_language_update:
{
"version": "1",
"default": "deny",
"tools": {
"natural_language_update": {
"limits": [
{
"counter": "natural_language_update_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}natural_language_update 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.
natural_language_update. It is categorised as a Write tool in the ServiceNow MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for natural_language_update: 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 ServiceNow MCP Server. Nothing to install.
natural_language_update 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 natural_language_update 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 natural_language_update. 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.
natural_language_update is provided by the ServiceNow MCP Server MCP server (michaelbuckner/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ServiceNow MCP Server, 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.
10 ServiceNow MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.