get_execution_results
AI agents call get_execution_results to retrieve information from Dune Analytics MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves results from previously executed queries, which is a read operation with no side effects. The empty description reduces confidence slightly, but the naming pattern and context (querying blockchain data from Dune Analytics) indicate result retrieval rather than execution or modification.
From the tool's definition Tool name 'get_execution_results' combined with sibling tools that include 'run_query' and 'submit_query' suggests this retrieves cached or completed query results. No parameters for modification, deletion, or execution are implied by the name.
Attacks that exploit this kind of access
get_execution_results. It is categorised as a Read tool in the Dune Analytics MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Dune Analytics MCP Server MCP server in PolicyLayer and add a rule for get_execution_results: 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.
get_execution_results 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 get_execution_results 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 get_execution_results. 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.
get_execution_results 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 →