gws_raw
Execute any Google Workspace CLI command. For advanced use when specific tools don
This record as markdown: /tools/heznpc-airmcp/gws-raw.md
What gws_raw does on AirMCP
AI agents invoke gws_raw to trigger actions in AirMCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why gws_raw is rated High
This tool allows execution of arbitrary Google Workspace CLI commands, giving an AI agent the ability to run any command supported by the gws CLI without apparent restrictions. This is Execute-category because it triggers external operations (CLI commands) whose effects depend on arguments.
From the tool's definition Tool name 'gws_raw' with description 'Execute any Google Workspace CLI command' indicates direct execution of arbitrary CLI commands.
Attacks that exploit this kind of access
The rule that runs gws_raw safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gws_raw, this is the rule to start with:
gws_raw stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AirMCP, apply this rule, and every gws_raw call is checked against it from then on.
Questions about gws_raw
Execute any Google Workspace CLI command. For advanced use when specific tools don. It is categorised as a Execute tool in the AirMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Air MCP server in PolicyLayer and add a rule for gws_raw: 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 AirMCP. Nothing to install.
gws_raw is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the gws_raw 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 gws_raw. 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.
gws_raw is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Air, and thousands of servers like it.
This server
Across the catalogue