update_grc_issue
Update a GRC Issue by sys_id. [Write — requires WRITE_ENABLED=true]
This record as markdown: /tools/tedorigawa001-servicenow-mcp/update-grc-issue.md
What update_grc_issue does on ServiceNow-MCP
AI agents use update_grc_issue 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_grc_issue is rated Medium
Updating GRC issues modifies existing records but does not irreversibly delete or destroy data. It is reversible (records can be updated again to restore prior state). This is a clear Write operation.
From the tool's definition Tool description explicitly states '[Write — requires WRITE_ENABLED=true]' and function is 'Update a GRC Issue by sys_id', indicating modification of existing data in ServiceNow's Governance, Risk, and Compliance module.
Attacks that exploit this kind of access
The rule that runs update_grc_issue 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 update_grc_issue, this is the rule to start with:
update_grc_issue 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 update_grc_issue call is checked against it from then on.
Questions about update_grc_issue
Update a GRC Issue by sys_id. [Write — requires WRITE_ENABLED=true]. 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 update_grc_issue: 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.
update_grc_issue 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 update_grc_issue 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 update_grc_issue. 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.
update_grc_issue 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