Runs the given sql query on Peaka. BEFORE RUNNING THIS TOOL: 1: Use peaka_get_project_metadata to determine which tables should be used in the query and their schemas. 2: Use peaka_list_tables to determine if the tables of interest are cached or not (this response has isCached pr...
Accepts freeform code/query input (query)
Part of the Peaka MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke peaka_execute_sql_query to trigger processes or run actions in Peaka. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
peaka_execute_sql_query can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
peaka_execute_sql_query:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Peaka policy for all 26 tools.
Agents calling execute-class tools like peaka_execute_sql_query have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
peaka_execute_sql_query is one of the high-risk operations in Peaka. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Runs the given sql query on Peaka. BEFORE RUNNING THIS TOOL: 1: Use peaka_get_project_metadata to determine which tables should be used in the query and their schemas. 2: Use peaka_list_tables to determine if the tables of interest are cached or not (this response has isCached property) 3: If one or more tables that you need to query are cacheable but not cached: 3a: Warn the user that the results will be limited and ask if you should start the caching process for those tables, and start the caching process using the create cache tool 3b: If the caching is rejected by the user, warn them that the query results will be limited and use LIMIT statements on the query to make sure it doesn't run forever If you do not already know the projectId for the current task, call peaka_list_projects first and ask the user which project to use. Remember the chosen projectId for subsequent calls in this conversation.. It is categorised as a Execute tool in the Peaka MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for peaka_execute_sql_query. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Peaka MCP server.
peaka_execute_sql_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 peaka_execute_sql_query rule in your Intercept 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 Intercept policy for peaka_execute_sql_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.
peaka_execute_sql_query is provided by the Peaka MCP server (@peaka/mcp-server-peaka). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.