New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

update_usem_rule

Update a USEM/VR automation rule by sys_id with a fields object restricted to that table allowlist.

SERVERServiceNow-MCP SOURCEtedorigawa001/servicenow-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/tedorigawa001-servicenow-mcp/update-usem-rule.md

What update_usem_rule does on ServiceNow-MCP

AI agents use update_usem_rule to create or update resources in ServiceNow-MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceNow-MCP environment.

Why update_usem_rule is rated Medium

The tool creates or modifies data reversibly by updating USEM/VR automation rules via a fields object. While it has high blast radius potential (misconfigured automation rules could trigger unintended incident responses, mass changes, or security policy violations across the infrastructure), it remains in the Write category rather than Execute because it modifies rule definitions themselves rather than executing…

From the tool's definition Tool name contains 'update' and description explicitly states 'Update a USEM/VR automation rule' — this modifies existing configuration data in ServiceNow's event management and vulnerability response automation system.

Questions about update_usem_rule

What does the update_usem_rule tool do? +

Update a USEM/VR automation rule by sys_id with a fields object restricted to that table allowlist. It is categorised as a Write tool in the ServiceNow-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_usem_rule? +

Register the ServiceNow MCP server in PolicyLayer and add a rule for update_usem_rule: 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. Nothing to install.

What risk level is update_usem_rule? +

update_usem_rule is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_usem_rule? +

Yes. Add a rate_limit block to the update_usem_rule 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.

How do I block update_usem_rule completely? +

Set action: deny in the PolicyLayer policy for update_usem_rule. 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.

What MCP server provides update_usem_rule? +

update_usem_rule is provided by the ServiceNow MCP server (tedorigawa001/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on ServiceNow, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of ServiceNow's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.