snow_instance_visibility
Report what this ServiceNow connection can actually see: per table whether the read succeeds (with the HTTP status and the row count behind it), which roles the account holds and which ones a refused table needs, whether javascript: date filters resolve on this instance or are silently dropped, w...
This record as markdown: /tools/serac/snow-instance-visibility.md
What snow_instance_visibility does on Serac
AI agents call snow_instance_visibility 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_instance_visibility is rated Low
Purely diagnostic, read-only tool that reports visibility and instance metadata.
From the tool's definition Read-only: every call is a GET
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs snow_instance_visibility 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_instance_visibility, this is the rule to start with:
snow_instance_visibility is read-only, so it stays allowed. 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_instance_visibility call is checked against it from then on.
Questions about snow_instance_visibility
Report what this ServiceNow connection can actually see: per table whether the read succeeds (with the HTTP status and the row count behind it), which roles the account holds and which ones a refused table needs, whether javascript: date filters resolve on this instance or are silently dropped, whether a condition on an unknown column is ignored or returns no rows, and which release, build, edition and plugin count answered. Call this when queries come back empty or a filtered count looks wrong, before trusting any number from this instance. Read-only: every call is a GET. It is categorised as a Read tool in the Serac MCP Server, which means it retrieves data without modifying state.
Register the Serac MCP server in PolicyLayer and add a rule for snow_instance_visibility: 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_instance_visibility is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the snow_instance_visibility 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_instance_visibility. 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_instance_visibility 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