snow_grc_risk_manage
Unified tool for ServiceNow GRC Advanced Risk register lifecycle: registering risks, scoring them, attaching treatment plans, and assigning ownership. Wraps the sn_risk_advanced_risk, sn_risk_risk_treatment, and sn_risk_risk_owner tables that ship with the GRC: Advanced Risk plugin. Actions: - li...
This record as markdown: /tools/serac/snow-grc-risk-manage.md
What snow_grc_risk_manage does on Serac
AI agents use snow_grc_risk_manage to create or update resources in Serac, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Serac environment.
Why snow_grc_risk_manage is rated Medium
This is a Write tool because it creates and modifies risk management data reversibly. While risk data is sensitive in an enterprise GRC context and misuse could have downstream consequences (e.g., incorrectly registering or scoring risks could affect compliance decisions), the operations themselves are not irreversible deletions (Destructive), financial transactions (Financial), or arbitrary code execution (Execute).
From the tool's definition The tool provides 'create' and 'assess' (update) actions on risk management records, explicitly modifying the sn_risk_advanced_risk, sn_risk_risk_treatment, and sn_risk_risk_owner tables.
Attacks that exploit this kind of access
The rule that runs snow_grc_risk_manage safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Serac, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For snow_grc_risk_manage, this is the rule to start with:
snow_grc_risk_manage 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 Serac, apply this rule, and every snow_grc_risk_manage call is checked against it from then on.
Questions about snow_grc_risk_manage
Unified tool for ServiceNow GRC Advanced Risk register lifecycle: registering risks, scoring them, attaching treatment plans, and assigning ownership. Wraps the sn_risk_advanced_risk, sn_risk_risk_treatment, and sn_risk_risk_owner tables that ship with the GRC: Advanced Risk plugin. Actions: - list — list risks, optionally filtered by category, state, or owner - get — retrieve a single risk by sys_id (includes counts of treatments and owners) - create — register a new risk with category, inherent score, and owner - assess — update the risk. It is categorised as a Write tool in the Serac MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Serac MCP server in PolicyLayer and add a rule for snow_grc_risk_manage: 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 Serac. Nothing to install.
snow_grc_risk_manage 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 snow_grc_risk_manage 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 snow_grc_risk_manage. 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.
snow_grc_risk_manage is provided by the Serac MCP server (serac-labs/serac). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Serac, and thousands of servers like it.
This server
Across the catalogue