snow_add_form_field
Add a field (element) to a form section by section sys_id, with optional field type and ordering position. Writes to sys_ui_element.
This record as markdown: /tools/serac/snow-add-form-field.md
What snow_add_form_field does on Serac
AI agents use snow_add_form_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_add_form_field is rated Medium
This tool creates new data (form fields) in the ServiceNow instance via writes to sys_ui_element table. The operation is reversible (fields can be deleted or modified later), making it Write rather than Destructive. However, unauthorized modifications to form definitions could disrupt user workflows and enable privilege escalation or data exfiltration via UI manipulation, warranting medium severity.
From the tool's definition Tool performs 'Add a field (element) to a form section' and 'Writes to sys_ui_element' — these operations create new form field records in ServiceNow's UI metadata layer.
Attacks that exploit this kind of access
The rule that runs snow_add_form_field 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_add_form_field, this is the rule to start with:
snow_add_form_field 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_add_form_field call is checked against it from then on.
Questions about snow_add_form_field
Add a field (element) to a form section by section sys_id, with optional field type and ordering position. Writes to sys_ui_element. 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_add_form_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.
snow_add_form_field 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_add_form_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.
Set action: deny in the PolicyLayer policy for snow_add_form_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.
snow_add_form_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.
More on Serac, and thousands of servers like it.
This server
Across the catalogue