bigquery_last_n_query · GCP MCP Log Diagnostics MCP

WHAT IT DOES

What bigquery_last_n_query does on GCP MCP Log Diagnostics

AI agents invoke bigquery_last_n_query to trigger actions in GCP MCP Log Diagnostics. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why bigquery_last_n_query needs a policy

The name implies running queries against BigQuery, which is an Execute-level action (running SQL that could be arbitrary). However, the empty description significantly lowers confidence. Given the server context (GCP log diagnostics), it likely retrieves recent query results, but 'query' execution against BigQuery warrants at least Execute classification.

From the tool's definition Tool name 'bigquery_last_n_query' suggests execution of BigQuery queries; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bigquery_last_n_query Rate-limited

bigquery_last_n_query stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bigquery_last_n_query": {
      "limits": [
        {
          "counter": "bigquery_last_n_query_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches GCP MCP Log Diagnostics, so you can run agents against it safely.

FAQ

Questions about bigquery_last_n_query

What does the bigquery_last_n_query tool do? +

bigquery_last_n_query. It is categorised as a Execute tool in the GCP MCP Log Diagnostics MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on bigquery_last_n_query? +

Register the GCP MCP Log Diagnostics MCP server in PolicyLayer and add a rule for bigquery_last_n_query: 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 GCP MCP Log Diagnostics. Nothing to install.

What risk level is bigquery_last_n_query? +

bigquery_last_n_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit bigquery_last_n_query? +

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

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

bigquery_last_n_query is provided by the GCP MCP Log Diagnostics MCP server (kanhaiworld/gcp_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.