run_sql
AI agents invoke run_sql to trigger actions in Dune Analytics 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 executes arbitrary SQL queries (DuneSQL) against a blockchain analytics database. While read-only queries are possible, SQL execution is a general-purpose capability that could be misused to extract sensitive data, perform expensive computations, or access unauthorized information depending on permissions and query complexity.
From the tool's definition Tool name 'run_sql' combined with server context describing 'execution of saved queries, ad-hoc DuneSQL queries' indicates the tool executes SQL queries against blockchain data.
Attacks that exploit this kind of access
run_sql. It is categorised as a Execute tool in the Dune Analytics MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Dune Analytics MCP Server MCP server in PolicyLayer and add a rule for run_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 Dune Analytics MCP Server. Nothing to install.
run_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 run_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 run_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.
run_sql is provided by the Dune Analytics MCP Server MCP server (sak1337/dune-mcp). 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 →