Unified tool for ServiceNow GRC Vendor Risk Management: vendor inventory, assessment kick-off, and linkage back to the central risk register. Wraps the sn_vdr_vendor, sn_vdr_assessment, and sn_vdr_question_template tables that ship with the GRC: Vendor Risk Management plugin. Actions: - list_vend...
AI agents use snow_grc_vendor_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.
While this tool includes read operations (list_vendors, list_assessments), the primary capability is assess_vendor which creates new sn_vdr_assessment records in draft state. This is a reversible modification of enterprise GRC data.
From the tool's definition Tool performs actions that create or modify data: 'list_vendors' (read), 'assess_vendor — kick off a vendor assessment... creates an sn_vdr_assessment row' (write), and 'list_assessments' (read).
Attacks that exploit this kind of access
Unified tool for ServiceNow GRC Vendor Risk Management: vendor inventory, assessment kick-off, and linkage back to the central risk register. Wraps the sn_vdr_vendor, sn_vdr_assessment, and sn_vdr_question_template tables that ship with the GRC: Vendor Risk Management plugin. Actions: - list_vendors — list vendors in the third-party inventory, optionally filtered by tier or active flag - assess_vendor — kick off a vendor assessment using a question template (creates an sn_vdr_assessment row in draft state) - list_assessments — list assessments, optionally filtered by vendor, state, or framework - create_assessment — create an assessment record directly with explicit fields (low-level alternative to assess_vendor) - link_to_risk — link a vendor assessment back to an entry in the central risk register (sn_risk_advanced_risk) Use when: the agent needs to drive third-party / vendor risk — inventorying vendors, kicking off questionnaire-based assessments, and connecting the vendor risk outcome to the central risk register. For internal risk register operations use snow_grc_risk_manage; for compliance issues and exceptions use snow_grc_issue_manage. Returns: vendor rows with sys_id, name, tier, active flag; assessment rows with state, template, scheduled date; question template rows with sys_id and name. GRC plugin gating: the first call against the vendor tables will surface a clear error if the GRC: Vendor Risk 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_vendor_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_vendor_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_vendor_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_vendor_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_vendor_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.
snow_grc_vendor_risk_manage is one line of Serac's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →