This record as markdown: /tools/deloc-mcp/connect-bigquery.md
What connect_bigquery does on Deloc
AI agents use connect_bigquery to create or update resources in Deloc, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Deloc environment.
Why connect_bigquery is rated Medium
Connecting a user to BigQuery involves creating an authentication session or credential, which modifies the user's configuration state. This is a write operation because it creates or establishes a new resource (a connection). It is not destructive because the connection can be disconnected or revoked. It is not execute because it doesn't run queries or arbitrary code.
From the tool's definition The tool name is 'connect_bigquery' and the description states 'Connect the user'. Combined with sibling tools like 'create_oauth_credential', this tool creates or establishes a new connection/authentication credential to BigQuery, which is a reversible write…
Attacks that exploit this kind of access
The rule that runs connect_bigquery 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 connect_bigquery, this is the rule to start with:
connect_bigquery stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 connect_bigquery call is checked against it from then on.
Questions about connect_bigquery
Connect the user. It is categorised as a Write tool in the Deloc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Deloc MCP server in PolicyLayer and add a rule for connect_bigquery: 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.
connect_bigquery is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the connect_bigquery 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 connect_bigquery. 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.
connect_bigquery 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