Report whether stored credentials are valid and loaded.
AI agents call auth_status to retrieve information from Hermes Google without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only check of credential validity. It queries internal state and reports results with no side effects, modifications, or command execution. The severity is low because exploiting this tool cannot access data, modify systems, or cause damage—it only reveals whether authentication is functional. Confidence is high because the function's intent is transparently a status/reporting operation.
From the tool's definition Tool name 'auth_status' and description 'Report whether stored credentials are valid and loaded' indicate a status query operation that retrieves authentication state without modifying or executing actions.
Attacks that exploit this kind of access
Report whether stored credentials are valid and loaded. It is categorised as a Read tool in the Hermes Google MCP Server, which means it retrieves data without modifying state.
Register the Hermes Google 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 Hermes Google. Nothing to install.
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 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 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.
auth_status is provided by the Hermes Google MCP server (jimmy-larsson/hermes-google). 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 →