list_tables_in_dataset

THE RISK

Low Risk

Why list_tables_in_dataset needs a policy

This tool retrieves and queries table metadata within a dataset—a classic Read operation. It has no capability to create, modify, delete, execute code, or transfer money. The blast radius of misuse is minimal: an agent could discover table names and schema, but cannot alter or access actual data beyond metadata inspection. The read-only context of the server further confirms this classification.

From the tool's definition Tool description states it 'List tables in dataset' with optional search and information retrieval. The server is explicitly described as enabling 'read-only queries'.

Documented attack patterns abuse exactly the kind of access list_tables_in_dataset gives an agent:

POLICY

How to control list_tables_in_dataset

PolicyLayer is an MCP gateway — it sits between your AI agents and BigQuery MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_tables_in_dataset:

policy.json

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

list_tables_in_dataset is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register BigQuery MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More BigQuery MCP Server tools

Execute run_query Execute read-only BigQuery SQL queries with safety validation. Use LIMIT in your query to Read get_table Get detailed table information with schema and column fill rate analysis Read list_datasets_in_project List all datasets in BigQuery project with optional search and detailed information Read vector_search Vector search: discover embedding tables (no query_text) or perform semantic search (with

All 5 BigQuery MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about list_tables_in_dataset

What does the list_tables_in_dataset tool do? +

List tables in dataset with optional search, detailed information, and dataset context. It is categorised as a Read tool in the BigQuery MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_tables_in_dataset? +

Register the BigQuery MCP Server MCP server in PolicyLayer and add a rule for list_tables_in_dataset: 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 BigQuery MCP Server. Nothing to install.

What risk level is list_tables_in_dataset? +

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

Can I rate-limit list_tables_in_dataset? +

Yes. Add a rate_limit block to the list_tables_in_dataset 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 list_tables_in_dataset completely? +

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

list_tables_in_dataset is provided by the BigQuery MCP Server MCP server (pvoo/bigquery-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every BigQuery MCP Server tool call.

Start from BigQuery MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →