snow_create_metric
Define a metric (metric_definition) over a table — count rows, or sum/avg/min/max a numeric field. Stored definition is later sampled by snow_collect_metric or platform schedulers.
This record as markdown: /tools/serac/snow-create-metric.md
What snow_create_metric does on Serac
AI agents use snow_create_metric 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_metric is rated Medium
The tool creates a metric definition that is stored in the system for later sampling/collection. This is a Write operation (creates new configuration data) rather than Read (query only) or Execute (triggers immediate external actions). The severity is medium because misconfiguration of metrics could affect monitoring/reporting but does not directly delete data or cause financial impact.
From the tool's definition Tool description states 'Define a metric' and 'Stored definition is later sampled' — this creates and persists a new metric definition object in ServiceNow, which is a reversible data modification.
Attacks that exploit this kind of access
The rule that runs snow_create_metric 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_metric, this is the rule to start with:
snow_create_metric 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_metric call is checked against it from then on.
Questions about snow_create_metric
Define a metric (metric_definition) over a table — count rows, or sum/avg/min/max a numeric field. Stored definition is later sampled by snow_collect_metric or platform schedulers. 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_metric: 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_metric 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_metric 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_metric. 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_metric 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