List all datasets in the BigQuery project. Use this first to discover what data is available.
AI agents call list_datasets to retrieve information from BigQuery MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves metadata about existing datasets without creating, modifying, deleting, or executing any operations. It is a safe discovery mechanism. Severity is low because unauthorized dataset enumeration alone poses minimal risk compared to actual data access or modification—the real sensitive operations would come from subsequent tools that query the discovered datasets.
From the tool's definition Tool name is 'list_datasets' and description states 'List all datasets in the BigQuery project.' The verb 'list' and the action of discovering available data indicate a read-only retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access list_datasets gives an agent:
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_datasets:
{
"version": "1",
"default": "deny",
"tools": {
"list_datasets": {}
}
}list_datasets is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all datasets in the BigQuery project. Use this first to discover what data is available. It is categorised as a Read tool in the BigQuery MCP Server MCP Server, which means it retrieves data without modifying state.
Register the BigQuery MCP Server MCP server in PolicyLayer and add a rule for list_datasets: 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.
list_datasets 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 list_datasets 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 list_datasets. 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.
list_datasets is provided by the BigQuery MCP Server MCP server (suganthan-mohanadasan/suganthans-bigquery-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 32 BigQuery MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
32 BigQuery MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.