snow_get_slow_queries

Retrieve slow database query logs for identifying performance issues, optimizing GlideRecord queries, and improving system responsiveness

Server Serac serac-labs/serac
Category Read
Risk class Low
Parameters 00 required

What snow_get_slow_queries does on Serac

AI agents call snow_get_slow_queries 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.

Why snow_get_slow_queries needs a policy

This tool retrieves and queries existing log data to identify performance issues. It has no side effects, does not execute code, does not modify data, and does not delete anything. While exposure of query logs could reveal some system internals, the blast radius from misuse is limited to information disclosure. The tool performs a diagnostic read operation typical of monitoring and observability features.

From the tool's definition Tool description states 'Retrieve slow database query logs' — a retrieval operation with no modification or execution of queries, only inspection of performance logs for diagnostic purposes.

Questions about snow_get_slow_queries

What does the snow_get_slow_queries tool do? +

Retrieve slow database query logs for identifying performance issues, optimizing GlideRecord queries, and improving system responsiveness. It is categorised as a Read tool in the Serac MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on snow_get_slow_queries? +

Register the Serac MCP server in PolicyLayer and add a rule for snow_get_slow_queries: 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.

What risk level is snow_get_slow_queries? +

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

Can I rate-limit snow_get_slow_queries? +

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

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

snow_get_slow_queries 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.

// THE FULL RECORD

snow_get_slow_queries 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.