Low Risk

get_records_from_table

Retrieves records from any specified table with advanced filtering, sorting, and pagination.

How to control get_records_from_table ↓

What get_records_from_table does on Snow

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

Low Risk

Why get_records_from_table needs a policy

This tool performs data retrieval only. The verbs 'retrieves' and the function of 'filtering, sorting, and pagination' are all read-only operations that do not create, modify, delete, or execute any changes to data. No side effects are described. This is a straightforward Read operation typical of query tools in data access APIs.

From the tool's definition Tool name 'get_records_from_table' and description 'Retrieves records from any specified table with advanced filtering, sorting, and pagination' indicate a query/retrieval operation with no modification or side effects.

Documented attack patterns abuse exactly the kind of access get_records_from_table gives an agent:

How to control get_records_from_table

PolicyLayer is an MCP gateway — it sits between your AI agents and Snow, and nothing reaches the server without passing your rules. This is the rule we recommend for get_records_from_table:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_records_from_table": {}
  }
}

get_records_from_table is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Snow — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_records_from_table

What does the get_records_from_table tool do? +

Retrieves records from any specified table with advanced filtering, sorting, and pagination. It is categorised as a Read tool in the Snow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_records_from_table? +

Register the Snow MCP server in PolicyLayer and add a rule for get_records_from_table: 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 Snow. Nothing to install.

What risk level is get_records_from_table? +

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

Can I rate-limit get_records_from_table? +

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

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

get_records_from_table is provided by the Snow MCP server (shunyaai/snow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Snow tool call.

Start from Snow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

88 Snow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.