vanna_generate_sql
AI agents use vanna_generate_sql to create or update resources in PostGIS Yukon MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PostGIS Yukon MCP environment.
An AI agent can call vanna_generate_sql faster than any human can review — one bad instruction and it creates or modifies resources in PostGIS Yukon MCP by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
vanna_generate_sql. It is categorised as a Write tool in the PostGIS Yukon MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PostGIS Yukon MCP server in PolicyLayer and add a rule for vanna_generate_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 PostGIS Yukon MCP. Nothing to install.
vanna_generate_sql is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the vanna_generate_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 vanna_generate_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.
vanna_generate_sql is provided by the PostGIS Yukon MCP server (zmgiser/postgis_yukon_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.