bigquery_list_tables

List the tables in a BigQuery dataset.

SERVERDeloc SOURCEdelocdev/deloc-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/deloc-mcp/bigquery-list-tables.md

WHAT IT DOES

What bigquery_list_tables does on Deloc

AI agents call bigquery_list_tables 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.

RISK

Why bigquery_list_tables is rated Low

This is a Read operation—it queries and retrieves data (table metadata) with no side effects. Severity is medium rather than low because BigQuery access can expose schema information that reveals business-sensitive data structures, datasets, or naming patterns that could inform further attacks or data exfiltration attempts.

From the tool's definition Tool name 'bigquery_list_tables' and description 'List the tables in a BigQuery dataset' indicate a query/list operation that retrieves metadata about BigQuery tables without modifying them.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs bigquery_list_tables 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 bigquery_list_tables, this is the rule to start with:

bigquery_list_tables Allowed

bigquery_list_tables is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bigquery_list_tables": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Deloc, apply this rule, and every bigquery_list_tables call is checked against it from then on.

FAQ

Questions about bigquery_list_tables

What does the bigquery_list_tables tool do? +

List the tables in a BigQuery dataset. It is categorised as a Read tool in the Deloc MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on bigquery_list_tables? +

Register the Deloc MCP server in PolicyLayer and add a rule for bigquery_list_tables: 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.

What risk level is bigquery_list_tables? +

bigquery_list_tables is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit bigquery_list_tables? +

Yes. Add a rate_limit block to the bigquery_list_tables 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.

How do I block bigquery_list_tables completely? +

Set action: deny in the PolicyLayer policy for bigquery_list_tables. 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.

What MCP server provides bigquery_list_tables? +

bigquery_list_tables 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.

KEEP EXPLORING

More on Deloc, and thousands of servers like it.

This server

All 45 Deloc tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →