AI agents invoke bigquery_run_query to trigger actions in Mimi Seed. 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.
BigQuery query execution is a classic Execute operation: it runs code (SQL) against an external service whose effects depend on the query arguments. Although the description hints at SELECT-only usage via '(SELECT)', the tool name and capability to 'run_query' indicate execution of arbitrary SQL statements.
From the tool's definition Tool name 'bigquery_run_query' combined with description stating it executes 'SQL 쿼리' (SQL queries) against BigQuery tables.
Attacks that exploit this kind of access
BigQuery SQL 쿼리 실행 (SELECT). GA4 analytics_* 테이블 분석에 사용. It is categorised as a Execute tool in the Mimi Seed MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mimi Seed MCP server in PolicyLayer and add a rule for bigquery_run_query: 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 Mimi Seed. Nothing to install.
bigquery_run_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 bigquery_run_query 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 bigquery_run_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.
bigquery_run_query is provided by the Mimi Seed MCP server (@yoonion/mimi-seed-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
bigquery_run_query is one line of Mimi Seed's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →