snow_create_field

Add a new column to a table by writing to sys_dictionary: column name, label, internal_type (string, integer, reference, etc.), and — for reference fields — the referenced table. Optional max_length and mandatory flag.

Server Serac serac-labs/serac
Category Write
Risk class Medium
Parameters 00 required

What snow_create_field does on Serac

AI agents use snow_create_field 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_field needs a policy

This tool creates new fields/columns in a ServiceNow table by modifying the sys_dictionary system table. While reversible (fields can be deleted), this is a schema-altering write operation that could break existing workflows, reports, or integrations if misused. The high severity reflects that an autonomous agent adding arbitrary fields to critical tables could cause business disruption.

From the tool's definition Tool description states 'Add a new column to a table by writing to sys_dictionary' — explicitly a write operation that creates new schema objects. Uses verbs 'Add' and 'writing to' which indicate modification of data structures.

Questions about snow_create_field

What does the snow_create_field tool do? +

Add a new column to a table by writing to sys_dictionary: column name, label, internal_type (string, integer, reference, etc.), and — for reference fields — the referenced table. Optional max_length and mandatory flag. 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.

How do I enforce a policy on snow_create_field? +

Register the Serac MCP server in PolicyLayer and add a rule for snow_create_field: 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.

What risk level is snow_create_field? +

snow_create_field is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit snow_create_field? +

Yes. Add a rate_limit block to the snow_create_field 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.

How do I block snow_create_field completely? +

Set action: deny in the PolicyLayer policy for snow_create_field. 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.

What MCP server provides snow_create_field? +

snow_create_field 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.

// THE FULL RECORD

snow_create_field 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.