Developer-only tool for testing ServiceNow connections, OAuth credentials, and table/column accessibility against a live instance. Use during tool development to validate assumptions (table existence, field names, query shape) before shipping production tools. Actions: - oauth — test arbitrary OA...
AI agents call snow_dev_test_connection to retrieve information from Serac without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool primarily reads and validates — it checks connectivity, verifies OAuth credentials, confirms table existence, and queries field metadata. No data is written, deleted, or executed. However, it does expose OAuth credentials and authentication context details, which raises the severity to medium due to potential credential leakage or reconnaissance value if misused by an agent.
From the tool's definition testing ServiceNow connections, OAuth credentials, and table/column accessibility against a live instance... validate assumptions (table existence, field names, query shape)
Attacks that exploit this kind of access
Developer-only tool for testing ServiceNow connections, OAuth credentials, and table/column accessibility against a live instance. Use during tool development to validate assumptions (table existence, field names, query shape) before shipping production tools. Actions: - oauth — test arbitrary OAuth credentials (instance + grant_type + client_id + secret, optional username/password for password grant). Returns redacted token info on success. - connection — verify the current authenticated context is healthy via a sys_user lookup. - table — verify a table exists and is accessible (sys_db_object lookup). Returns table label, parent class, and scope. - columns — list a table. 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_dev_test_connection: 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_dev_test_connection 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_dev_test_connection 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_dev_test_connection. 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_dev_test_connection 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.
snow_dev_test_connection 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 →