Ensure auth_clients.json exists for single-MCP multi-client auth routing.
AI agents use setup_google_auth_clients to create or update resources in Google Workspace Mcp Advanced — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Workspace Mcp Advanced environment.
This tool creates or modifies the `auth_clients.json` file needed for authentication routing. While it modifies data (the config file), the operation is reversible—the file can be edited or deleted. This is a Write operation rather than Execute because it doesn't run arbitrary code or shell commands.
From the tool's definition Tool description states it ensures `auth_clients.json` exists, which involves creating or modifying a configuration file. The verb 'ensure' combined with file path reference indicates file creation/writing operations.
Attacks that exploit this kind of access
Ensure auth_clients.json exists for single-MCP multi-client auth routing. It is categorised as a Write tool in the Google Workspace Mcp Advanced MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Workspace Mcp Advanced MCP server in PolicyLayer and add a rule for setup_google_auth_clients: 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 Google Workspace Mcp Advanced. Nothing to install.
setup_google_auth_clients is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the setup_google_auth_clients 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 setup_google_auth_clients. 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.
setup_google_auth_clients is provided by the Google Workspace Mcp Advanced MCP server (skeptomenos/google-workspace-mcp-advanced). 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 →