snow_test_acl
Simulate whether a user would be granted a given operation (read/write/create/delete) on a table or specific record under the current ACL configuration. Runs a server-side script using GlideRecord.canRead/canWrite/canCreate/canDelete.
This record as markdown: /tools/serac/snow-test-acl.md
What snow_test_acl does on Serac
AI agents call snow_test_acl 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_test_acl is rated Low
This tool queries the ACL configuration and permission system to determine if hypothetical operations would be allowed. It does not execute those operations, create, modify, or delete data—it only reads and evaluates the current security policy state. The blast radius of misuse is minimal: an agent could only learn what permissions exist, not abuse them to access unauthorized data or modify systems.
From the tool's definition Tool simulates and checks permissions (canRead/canWrite/canCreate/canDelete) without modifying any data or performing actual operations.
Attacks that exploit this kind of access
The rule that runs snow_test_acl 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_test_acl, this is the rule to start with:
snow_test_acl 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_test_acl call is checked against it from then on.
Questions about snow_test_acl
Simulate whether a user would be granted a given operation (read/write/create/delete) on a table or specific record under the current ACL configuration. Runs a server-side script using GlideRecord.canRead/canWrite/canCreate/canDelete. 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_test_acl: 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_test_acl 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_test_acl 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_test_acl. 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_test_acl 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