set_usem_rule_active
Enable or disable a USEM/VR rule (convenience toggle of the active flag).
This record as markdown: /tools/tedorigawa001-servicenow-mcp/set-usem-rule-active.md
What set_usem_rule_active does on ServiceNow-MCP
AI agents use set_usem_rule_active 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 set_usem_rule_active is rated Medium
This tool creates or modifies data (the active flag of USEM/VR rules) reversibly. Toggling a rule's active status is a Write operation—it changes system configuration but is not destructive (rules can be re-enabled) and does not delete data. The severity is medium because disabling critical rules could disrupt incident/change management workflows, but the change is reversible and doesn't destroy data or move money.
From the tool's definition "Enable or disable a USEM/VR rule (convenience toggle of the active flag)" — the tool modifies the active/inactive state of a rule, which is a reversible state change.
Attacks that exploit this kind of access
The rule that runs set_usem_rule_active safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_usem_rule_active, this is the rule to start with:
set_usem_rule_active 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.
The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow-MCP, apply this rule, and every set_usem_rule_active call is checked against it from then on.
Questions about set_usem_rule_active
Enable or disable a USEM/VR rule (convenience toggle of the active flag). 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.
Register the ServiceNow MCP server in PolicyLayer and add a rule for set_usem_rule_active: 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.
set_usem_rule_active 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 set_usem_rule_active 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 set_usem_rule_active. 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.
set_usem_rule_active 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.
This server
Across the catalogue