check_table_freshness

Check when a table was last updated (requires a timestamp column)

Server Snowflake MCP Server legolasan/snowflake_mcp
Category Read
Risk class Low
Parameters 00 required

What check_table_freshness does on Snowflake MCP Server

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

Why check_table_freshness needs a policy

This tool retrieves metadata about table freshness without modifying, deleting, or executing code. It is a passive query operation that examines existing data attributes. The blast radius of misuse is minimal—an agent could only gather information about update timing, not alter data or trigger external systems. Severity is low because exposure of table freshness metadata poses minimal security or operational risk.

From the tool's definition Tool description states it 'checks when a table was last updated' by reading timestamp metadata. It requires a timestamp column but performs no modification, deletion, or execution of arbitrary operations.

Questions about check_table_freshness

What does the check_table_freshness tool do? +

Check when a table was last updated (requires a timestamp column). It is categorised as a Read tool in the Snowflake MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_table_freshness? +

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

What risk level is check_table_freshness? +

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

Can I rate-limit check_table_freshness? +

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

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

check_table_freshness is provided by the Snowflake MCP Server MCP server (legolasan/snowflake_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

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.