Low Risk

get_schema_statistics

Get schema statistics information

How to control get_schema_statistics ↓

What get_schema_statistics does on MCP SQL Server

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

Low Risk

Why get_schema_statistics needs a policy

This tool retrieves statistical metadata about database schema (likely cardinality, distribution, indexes, etc.). It performs no writes, deletions, or code execution. The blast radius of misuse is minimal—an AI agent could only learn information about table structures and statistics, which is inherently non-destructive.

From the tool's definition Tool name 'get_schema_statistics' and description 'Get schema statistics information' indicate a data retrieval operation with no modification or execution capabilities.

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

How to control get_schema_statistics

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

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

get_schema_statistics 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 MCP SQL Server — 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_schema_statistics

What does the get_schema_statistics tool do? +

Get schema statistics information. It is categorised as a Read tool in the MCP SQL Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_schema_statistics? +

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

What risk level is get_schema_statistics? +

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

Can I rate-limit get_schema_statistics? +

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

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

get_schema_statistics is provided by the MCP SQL Server MCP server (ryudg/mcp-sql). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP SQL Server tool call.

Start from MCP SQL 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.

11 MCP SQL Server 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.