snow_create_data_policy
Create a Data Policy (sys_data_policy2) on a table — server-side equivalent of UI Policies, enforced for API/import writes. reverse_if_false re-applies the inverse when the condition turns false. Add field-level rules with snow_create_data_policy_rule.
This record as markdown: /tools/serac/snow-create-data-policy.md
What snow_create_data_policy does on Serac
AI agents use snow_create_data_policy 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_create_data_policy is rated Medium
This tool creates new policy records in ServiceNow that enforce constraints on data writes at the API and import level. While reversible (can be deleted), it modifies system behavior and enforces rules that affect all subsequent API operations. This is clearly a Write operation rather than Read (retrieves data) or Destructive (the policy itself is not deleted, just created).
From the tool's definition 'Create a Data Policy' — creates a new sys_data_policy2 record on a table. This is a data creation operation that establishes server-side enforcement rules affecting API/import writes.
Attacks that exploit this kind of access
The rule that runs snow_create_data_policy 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_create_data_policy, this is the rule to start with:
snow_create_data_policy 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_create_data_policy call is checked against it from then on.
Questions about snow_create_data_policy
Create a Data Policy (sys_data_policy2) on a table — server-side equivalent of UI Policies, enforced for API/import writes. reverse_if_false re-applies the inverse when the condition turns false. Add field-level rules with snow_create_data_policy_rule. 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_create_data_policy: 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_create_data_policy 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_create_data_policy 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_create_data_policy. 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_create_data_policy 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