snow_csm_contract_manage
Wraps ast_contract (asset contract) + service_entitlement + service_offering. CSM (com.sn_customerservice) does not have native contract tables; ast_contract is the closest functional equivalent and service_entitlement.contract is a native reference to it. Actions: - list_contracts — query ast_co...
This record as markdown: /tools/serac/snow-csm-contract-manage.md
What snow_csm_contract_manage does on Serac
AI agents use snow_csm_contract_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_csm_contract_manage is rated Medium
The tool performs multiple operations across the spectrum, but the create_contract action is a reversible write operation that modifies ServiceNow's contract database. While list and get operations are read-only, the creation capability is the most severe function exposed.
From the tool's definition Tool description explicitly includes 'create_contract — create an ast_contract' action, which creates new data records. Also includes 'list_contracts' (Read) and 'get_contract' (Read), but the presence of create capability elevates this to Write category.
Attacks that exploit this kind of access
The rule that runs snow_csm_contract_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_csm_contract_manage, this is the rule to start with:
snow_csm_contract_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_csm_contract_manage call is checked against it from then on.
Questions about snow_csm_contract_manage
Wraps ast_contract (asset contract) + service_entitlement + service_offering. CSM (com.sn_customerservice) does not have native contract tables; ast_contract is the closest functional equivalent and service_entitlement.contract is a native reference to it. Actions: - list_contracts — query ast_contract, optional filters: account, vendor, customer, state, active_only - get_contract — fetch one ast_contract row by sys_id or number, with related entitlement and offering counts - create_contract — create an ast_contract; vendor + vendor_contract + contract_model are required by the schema - list_entitlements — query service_entitlement, optional filters: contract, account, asset, active_only - link_entitlement_to_contract — set service_entitlement.contract on an existing entitlement (the schema. 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_csm_contract_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_csm_contract_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_csm_contract_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_csm_contract_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_csm_contract_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