workspace_connect · Gworkspace MCP: Risk & Policy

WHAT IT DOES

What workspace_connect does on Gworkspace

AI agents call workspace_connect as a supporting operation in Gworkspace workflows.

WHY IT NEEDS A POLICY

Why workspace_connect needs a policy

With no description available, the tool name 'workspace_connect' suggests an authentication or connection setup operation, which doesn't clearly fit Read, Write, Execute, Destructive, or Financial categories. It likely establishes a connection/session to Google Workspace, which is more of an initialization step. Confidence is low due to the empty description.

From the tool's definition Tool name is 'workspace_connect' and the description is empty or uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

workspace_connect Rate-limited

workspace_connect gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "workspace_connect": {
      "limits": [
        {
          "counter": "workspace_connect_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Gworkspace, so you can run agents against it safely.

FAQ

Questions about workspace_connect

What does the workspace_connect tool do? +

workspace_connect. It is categorised as a Other tool in the Gworkspace MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on workspace_connect? +

Register the Gworkspace MCP server in PolicyLayer and add a rule for workspace_connect: 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 Gworkspace. Nothing to install.

What risk level is workspace_connect? +

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

Can I rate-limit workspace_connect? +

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

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

workspace_connect is provided by the Gworkspace MCP server (leoonic/gworkspace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.