New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

snow_get_by_sysid

Get any ServiceNow record by sys_id with optional field selection

SERVERSerac SOURCEserac-labs/serac
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/serac/snow-get-by-sysid.md

What snow_get_by_sysid does on Serac

AI agents call snow_get_by_sysid to retrieve information from Serac without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why snow_get_by_sysid is rated Low

This tool retrieves data from ServiceNow by a unique identifier. While it can access any record (broad scope), the operation itself is read-only with no mutation, creation, deletion, or execution of code. The severity is low because data retrieval alone has minimal blast radius unless the data itself is sensitive, but misuse would manifest as information disclosure rather than system compromise or data loss.

From the tool's definition Tool name 'snow_get_by_sysid' and description 'Get any ServiceNow record by sys_id with optional field selection' indicate a retrieval operation.

Questions about snow_get_by_sysid

What does the snow_get_by_sysid tool do? +

Get any ServiceNow record by sys_id with optional field selection. It is categorised as a Read tool in the Serac MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on snow_get_by_sysid? +

Register the Serac MCP server in PolicyLayer and add a rule for snow_get_by_sysid: 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_get_by_sysid? +

snow_get_by_sysid is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit snow_get_by_sysid? +

Yes. Add a rate_limit block to the snow_get_by_sysid 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_get_by_sysid completely? +

Set action: deny in the PolicyLayer policy for snow_get_by_sysid. 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_get_by_sysid? +

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Serac's. Pull the full record:

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.