Report the startup error and remediation steps.
AI agents call server_status 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.
This tool reports system status and error information, which is a read-only operation with no side effects. It provides diagnostic output to help operators understand the current state of the server. The blast radius is minimal—an AI agent cannot misuse this to cause harm, only to gather status information about the server itself.
From the tool's definition Tool name 'server_status' and description 'Report the startup error and remediation steps' indicate retrieval of diagnostic/status information only. No data modification, deletion, code execution, or financial operations are performed.
Documented attack patterns abuse exactly the kind of access server_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Snowflake MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for server_status:
{
"version": "1",
"default": "deny",
"tools": {
"server_status": {}
}
}server_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Report the startup error and remediation steps. It is categorised as a Read tool in the Snowflake MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Snowflake MCP Server MCP server in PolicyLayer and add a rule for server_status: 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.
server_status 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 server_status 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 server_status. 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.
server_status is provided by the Snowflake MCP Server MCP server (ncejda-g2/snowflake_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Snowflake MCP Server, 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.
7 Snowflake MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.