snow_compliance_manage
Unified tool for ServiceNow compliance lifecycle beyond rule authoring and scanning: list_exceptions, exception_create, evidence_link, evidence_list, mark_compliant. Wraps the GRC tables sn_compliance_policy_exception, sn_compliance_control, and sn_compliance_evidence. Actions: - list_exceptions ...
This record as markdown: /tools/serac/snow-compliance-manage.md
What snow_compliance_manage does on Serac
AI agents use snow_compliance_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_compliance_manage is rated Medium
The tool primarily performs Write operations (create, link) on compliance governance records. While list_exceptions and evidence_list are Read operations, the tool's headline capability is exception_create and evidence_link, which create or modify compliance exception and evidence records.
From the tool's definition exception_create allows opening new policy exceptions with justification and expiry; evidence_link attaches evidence records to controls.
Attacks that exploit this kind of access
The rule that runs snow_compliance_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_compliance_manage, this is the rule to start with:
snow_compliance_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_compliance_manage call is checked against it from then on.
Questions about snow_compliance_manage
Unified tool for ServiceNow compliance lifecycle beyond rule authoring and scanning: list_exceptions, exception_create, evidence_link, evidence_list, mark_compliant. Wraps the GRC tables sn_compliance_policy_exception, sn_compliance_control, and sn_compliance_evidence. Actions: - list_exceptions — list policy exceptions, optionally filtered by control, state, or framework - exception_create — open a new policy exception against a control with justification and expiry - evidence_link — attach an existing evidence record (or arbitrary URL) to a control - evidence_list — list evidence rows linked to a given control - mark_compliant — set a control. 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_compliance_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_compliance_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_compliance_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_compliance_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_compliance_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