bigquery_auth_status

현재 BigQuery 인증 상태 조회 — 어떤 인증(서비스 계정/OAuth)이 사용되는지 확인

SERVERMimi Seed SOURCE@yoonion/mimi-seed-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/yoonion-mimi-seed-mcp/bigquery-auth-status.md

WHAT IT DOES

What bigquery_auth_status does on Mimi Seed

AI agents call bigquery_auth_status to retrieve information from Mimi Seed 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_auth_status is rated Low

This tool performs a read-only information retrieval operation. It checks the authentication configuration state without making any changes to data, executing commands, or triggering external operations. The severity is low because exposing authentication status alone does not create immediate operational risk, though the information could inform further attacks.

From the tool's definition The tool name 'bigquery_auth_status' and description indicate it 'queries/checks the current BigQuery authentication status' (조회 — 확인 means 'query/check').

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs bigquery_auth_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mimi Seed, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bigquery_auth_status, this is the rule to start with:

bigquery_auth_status Allowed

bigquery_auth_status 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_auth_status": {}
  }
}

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

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

FAQ

Questions about bigquery_auth_status

What does the bigquery_auth_status tool do? +

현재 BigQuery 인증 상태 조회 — 어떤 인증(서비스 계정/OAuth)이 사용되는지 확인. It is categorised as a Read tool in the Mimi Seed MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on bigquery_auth_status? +

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

What risk level is bigquery_auth_status? +

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

Can I rate-limit bigquery_auth_status? +

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

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

bigquery_auth_status is provided by the Mimi Seed MCP server (@yoonion/mimi-seed-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mimi Seed, and thousands of servers like it.

This server

All 230 Mimi Seed tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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