AI agents invoke turso_execute_sql to trigger actions in UnClick. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
org | string | Yes | |
sql | string | Yes | SQL statement to execute |
api_key | string | Yes | |
db_name | string | Yes | Database name |
Parameters from the server's own tool schema.
SQL query execution is classified as Execute rather than Destructive because the capability to perform destructive operations depends on the arguments passed and database permissions, not the tool itself. However, the severity is high because unrestricted SQL execution poses significant risk: an AI agent could be tricked into running queries that exfiltrate data, modify records, or corrupt the database.
From the tool's definition Tool description explicitly states 'Execute a SQL query' — this permits arbitrary SQL execution against a database.
Risk signalsAccepts freeform code/query input (sql) · Handles credentials or secrets (api_key)
Attacks that exploit this kind of access
Execute a SQL query against a Turso edge database. It is categorised as a Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
turso_execute_sql accepts 4 parameters: org, sql, api_key, db_name. Required: org, sql, api_key, db_name. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for turso_execute_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 UnClick. Nothing to install.
turso_execute_sql 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 turso_execute_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 turso_execute_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.
turso_execute_sql is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →