Low Risk

get_all_column_references

Extract column references from SQL statement with table context

How to control get_all_column_references ↓

What get_all_column_references does on Sql Analyzer

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

Low Risk

Why get_all_column_references needs a policy

This tool retrieves and analyzes metadata from SQL code without executing queries, modifying data, or triggering side effects. It is safe read-only analysis functionality. Severity is low because even if misused by an agent, the output is metadata only and cannot affect data or systems.

From the tool's definition Tool extracts column references from SQL statements—a pure parsing/analysis operation with no modification, execution, or deletion.

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

How to control get_all_column_references

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

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

get_all_column_references 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 Sql Analyzer — 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_all_column_references

What does the get_all_column_references tool do? +

Extract column references from SQL statement with table context. It is categorised as a Read tool in the Sql Analyzer MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_all_column_references? +

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

What risk level is get_all_column_references? +

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

Can I rate-limit get_all_column_references? +

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

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

get_all_column_references is provided by the Sql Analyzer MCP server (j4c0bs/mcp-server-sql-analyzer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Sql Analyzer tool call.

Start from Sql Analyzer, 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.

4 Sql Analyzer 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.