snow_grc_policy_manage
Unified tool for ServiceNow GRC policy authoring and linkage. Wraps the sn_compliance_policy, sn_compliance_policy_statement, sn_compliance_control_objective, and sn_compliance_control tables that ship with the GRC: Policy and Compliance Management plugin. Actions: - list_policies — list policies...
This record as markdown: /tools/serac/snow-grc-policy-manage.md
What snow_grc_policy_manage does on Serac
AI agents use snow_grc_policy_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_policy_manage is rated Medium
The tool primarily creates and modifies policy documents and compliance statements within ServiceNow's GRC system. While it includes read operations (list_policies, get_policy), the presence of create_policy and create_statement operations makes this a Write tool.
From the tool's definition Tool description states it 'Wraps' GRC policy tables and includes actions: 'create_policy' and 'create_statement' which create new policies and policy statements in ServiceNow's compliance system. These are reversible write operations.
Attacks that exploit this kind of access
The rule that runs snow_grc_policy_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_policy_manage, this is the rule to start with:
snow_grc_policy_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_policy_manage call is checked against it from then on.
Questions about snow_grc_policy_manage
Unified tool for ServiceNow GRC policy authoring and linkage. Wraps the sn_compliance_policy, sn_compliance_policy_statement, sn_compliance_control_objective, and sn_compliance_control tables that ship with the GRC: Policy and Compliance Management plugin. Actions: - list_policies — list policies, optionally filtered by state, type, or framework - get_policy — retrieve a single policy by sys_id (includes counts of linked statements) - create_policy — draft a new policy with owner, type, and effective date - create_statement — add a policy statement (clause / requirement) to an existing policy - link_to_control — link a policy statement to a control objective, attaching the policy intent to the control framework - list_controls — list controls, optionally filtered by objective or active flag Use when: the agent needs to draft a new GRC policy, break it into statements, and connect those statements to the control objectives that operationalise them. For the downstream exception / evidence / attestation flow on individual controls, use snow_compliance_manage; for the generic security policy record, use snow_create_security_policy. Returns: policy rows with sys_id, owner, type, state, effective_date; statement rows with sys_id, policy reference, statement_text; control objective and control rows with sys_id, name, and reference linkage. GRC plugin gating: the first call against these tables will surface a clear error if the GRC: Policy and Compliance Management plugin is not active on the target instance. 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_policy_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_policy_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_policy_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_policy_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_policy_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