check_bigquery_connection
Check whether a pending BigQuery connect session (started with connect_bigquery) has been approved. Polls briefly and reports the result.
This record as markdown: /tools/deloc-mcp/check-bigquery-connection.md
What check_bigquery_connection does on Deloc
AI agents call check_bigquery_connection to retrieve information from Deloc without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_bigquery_connection is rated Low
This tool only queries the status of an existing BigQuery connection session. It performs a read operation to determine whether a user has approved a pending OAuth/connection request. There is no data modification, deletion, code execution, or financial impact. The polling mechanism is a standard asynchronous check pattern.
From the tool's definition Tool description states it 'checks' and 'polls' a pending connection status and 'reports the result' — pure information retrieval with no side effects or state modifications.
Attacks that exploit this kind of access
The rule that runs check_bigquery_connection safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deloc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_bigquery_connection, this is the rule to start with:
check_bigquery_connection is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Deloc, apply this rule, and every check_bigquery_connection call is checked against it from then on.
Questions about check_bigquery_connection
Check whether a pending BigQuery connect session (started with connect_bigquery) has been approved. Polls briefly and reports the result. It is categorised as a Read tool in the Deloc MCP Server, which means it retrieves data without modifying state.
Register the Deloc MCP server in PolicyLayer and add a rule for check_bigquery_connection: 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 Deloc. Nothing to install.
check_bigquery_connection 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 check_bigquery_connection 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 check_bigquery_connection. 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.
check_bigquery_connection is provided by the Deloc MCP server (delocdev/deloc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Deloc, and thousands of servers like it.
This server
Across the catalogue