google-workspace.health

Check Google Workspace connector health and authentication status

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

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/cowork-os/google-workspace.health.md

WHAT IT DOES

What google-workspace.health does on CoWork OS

AI agents call google-workspace.health to retrieve information from CoWork OS without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why google-workspace.health is rated Low

This tool queries the health and authentication status of a connector, which is a read-only diagnostic operation with no side effects. Misuse potential is minimal as it only retrieves status information.

From the tool's definition Check Google Workspace connector health and authentication status

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs google-workspace.health safely

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

google-workspace.health Allowed

google-workspace.health 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": {
    "google-workspace.health": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every google-workspace.health call is checked against it from then on.

FAQ

Questions about google-workspace.health

What does the google-workspace.health tool do? +

Check Google Workspace connector health and authentication status. It is categorised as a Read tool in the CoWork OS MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on google-workspace.health? +

Register the CoWork OS MCP server in PolicyLayer and add a rule for google-workspace.health: 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 CoWork OS. Nothing to install.

What risk level is google-workspace.health? +

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

Can I rate-limit google-workspace.health? +

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

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

google-workspace.health is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools →

Across the catalogue

The MCP Attack Database →

Guides

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