AI agents call lint_sql 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.
SQL linting analyzes code structure and reports issues without executing queries, modifying data, or triggering external operations. This is a read-only analytical operation with no side effects. Confidence is slightly reduced due to missing tool-specific description, but the server context and sibling tools (all non-destructive analysis operations) strongly support the Read classification.
From the tool's definition Tool name 'lint_sql' combined with server description stating 'SQL analysis, linting' indicates static analysis of SQL code.
Documented attack patterns abuse exactly the kind of access lint_sql gives an agent:
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 lint_sql:
{
"version": "1",
"default": "deny",
"tools": {
"lint_sql": {}
}
}lint_sql 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.
lint_sql. It is categorised as a Read tool in the Sql Analyzer MCP Server, which means it retrieves data without modifying state.
Register the Sql Analyzer MCP server in PolicyLayer and add a rule for lint_sql: 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.
lint_sql 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 lint_sql 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 lint_sql. 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.
lint_sql 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.
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.