Check if the Google Docs MCP server is properly authenticated
AI agents call check_auth_status to retrieve information from LLM2Docs (Unofficial) without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple authentication status check, which is a read-only operation that queries the current state of authentication without modifying data, executing code, or performing any destructive actions. The blast radius of misuse is minimal, as it only returns authentication state information.
From the tool's definition Tool name and description indicate it 'Check[s] if the Google Docs MCP server is properly authenticated' — a status query operation with no data retrieval, modification, or execution capabilities.
Attacks that exploit this kind of access
Check if the Google Docs MCP server is properly authenticated. It is categorised as a Read tool in the LLM2Docs (Unofficial) MCP Server, which means it retrieves data without modifying state.
Register the LLM2Docs (Unofficial) MCP server in PolicyLayer and add a rule for check_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 LLM2Docs (Unofficial). Nothing to install.
check_auth_status 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 check_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.
Set action: deny in the PolicyLayer policy for check_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.
check_auth_status is provided by the LLM2Docs (Unofficial) MCP server (nomannayeem/google-docs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →