Doğal dilde sorulan soruyu anla ve uygun veritabanı sorgusuna çevir
AI agents invoke smart-query to trigger actions in PostGIS MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool translates natural language into database queries and executes them. Since the generated SQL is dynamic and unpredictable, it could produce SELECT, INSERT, UPDATE, DELETE, or even DROP statements depending on interpretation.
From the tool's definition 'uygun veritabanı sorgusuna çevir' (translate to appropriate database query) — converts natural language to database queries and executes them against a PostGIS database
Documented attack patterns abuse exactly the kind of access smart-query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PostGIS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for smart-query:
{
"version": "1",
"default": "deny",
"tools": {
"smart-query": {
"limits": [
{
"counter": "smart-query_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}smart-query stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Doğal dilde sorulan soruyu anla ve uygun veritabanı sorgusuna çevir. It is categorised as a Execute tool in the PostGIS MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the PostGIS MCP Server MCP server in PolicyLayer and add a rule for smart-query: 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 PostGIS MCP Server. Nothing to install.
smart-query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the smart-query 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 smart-query. 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.
smart-query is provided by the PostGIS MCP Server MCP server (receptopalak/postgis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PostGIS 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.
25 PostGIS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.