auth_status

SERVERMcp Google Docs SOURCE@a1-x-tech/mcp-google-docs

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/a1-x-tech-mcp-google-docs/auth-status.md

WHAT IT DOES

What auth_status does on Mcp Google Docs

AI agents call auth_status to retrieve information from Mcp Google Docs without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why auth_status is rated Low

Even though auth_status only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs auth_status safely

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

auth_status Allowed

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

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

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

FAQ

Questions about auth_status

What does the auth_status tool do? +

Shows whether this server is connected to Google: token presence and source (env variables or a stored in-chat login), expiry, the Google account email, granted vs missing OAuth scopes, where the credentials file lives and where the OAuth client comes from. Makes no network calls and never returns the token itself. Call it first when other tools report the server is not connected. It is categorised as a Read tool in the Mcp Google Docs MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on auth_status? +

Register the Mcp Google Docs MCP server in PolicyLayer and add a rule for 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 Mcp Google Docs. Nothing to install.

What risk level is auth_status? +

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

Can I rate-limit auth_status? +

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

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

auth_status is provided by the Mcp Google Docs MCP server (@a1-x-tech/mcp-google-docs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Google Docs, and thousands of servers like it.

This server

All 27 Mcp Google Docs tools →

Across the catalogue

editor_status on 010 Editor → The MCP Attack Database →

Guides

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