snow_grc_audit_manage
Unified tool for ServiceNow GRC Audit Management: engagements, audits, findings, and evidence. Wraps the sn_audit_audit, sn_audit_finding, sn_audit_engagement, and sn_audit_evidence tables that ship with the GRC: Audit Management plugin. Actions: - list — list audits, optionally filtered by engag...
This record as markdown: /tools/serac/snow-grc-audit-manage.md
What snow_grc_audit_manage does on Serac
AI agents use snow_grc_audit_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_audit_manage is rated Medium
While the tool includes read operations (list, get), the presence of create_audit and update_audit places it in the Write category. The severity is high because misuse could create false audit records, add misleading findings, or modify critical compliance documentation in ServiceNow, affecting governance and audit trails.
From the tool's definition Tool performs create_audit, update_audit, and add_finding operations that create or modify data in ServiceNow GRC audit tables (sn_audit_audit, sn_audit_finding, sn_audit_engagement, sn_audit_evidence). These are reversible write operations.
Attacks that exploit this kind of access
The rule that runs snow_grc_audit_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_audit_manage, this is the rule to start with:
snow_grc_audit_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_audit_manage call is checked against it from then on.
Questions about snow_grc_audit_manage
Unified tool for ServiceNow GRC Audit Management: engagements, audits, findings, and evidence. Wraps the sn_audit_audit, sn_audit_finding, sn_audit_engagement, and sn_audit_evidence tables that ship with the GRC: Audit Management plugin. Actions: - list — list audits, optionally filtered by engagement, state, or auditor - get — retrieve a single audit by sys_id - create_audit — open a new audit inside an existing engagement - update_audit — patch fields on an existing audit (state, scope, lead auditor, dates) - add_finding — log a finding against an audit with severity and recommendation - list_findings — list findings, optionally filtered by audit, severity, or state - attach_evidence — attach an evidence record (or external URL) to an audit or finding Use when: the agent needs to drive an audit engagement end to end — opening individual audits, logging the findings that come out of them, and attaching the evidence collected during fieldwork. For policy and control evidence outside an audit context, use snow_compliance_manage; for risk register operations, use snow_grc_risk_manage. Returns: audit rows with sys_id, engagement, state, lead auditor, planned and actual dates; finding rows with severity, recommendation, target remediation date; evidence rows with type and reference link. GRC plugin gating: the first call against the audit tables will surface a clear error if the GRC: Audit 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_audit_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_audit_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_audit_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_audit_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_audit_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