Check connection health for all configured Google accounts. Shows token status and last action.
AI agents call google_status to retrieve information from Mariana Google MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a status/health check tool that retrieves diagnostic information about account connections and recent activity. It performs read-only queries returning system state information. There is no capability to modify, delete, execute external code, or commit financial transactions.
From the tool's definition Tool name and description indicate it 'Check[s] connection health' and 'Shows token status and last action' — purely diagnostic queries with no side effects, data modification, or external operations triggered.
Attacks that exploit this kind of access
Check connection health for all configured Google accounts. Shows token status and last action. It is categorised as a Read tool in the Mariana Google MCP MCP Server, which means it retrieves data without modifying state.
Register the Mariana Google MCP server in PolicyLayer and add a rule for google_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 Mariana Google MCP. Nothing to install.
google_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 google_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 google_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.
google_status is provided by the Mariana Google MCP server (marianasmall/mariana-google-mcp). 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 →