configure_todrive_noemail · GAM MCP Server MCP

WHAT IT DOES

What configure_todrive_noemail does on GAM MCP Server

AI agents use configure_todrive_noemail to create or update resources in GAM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GAM MCP Server environment.

WHY IT NEEDS A POLICY

Why configure_todrive_noemail needs a policy

The tool likely modifies Drive configuration settings (disabling email notifications on Drive events or similar). This is a reversible Write action affecting Google Workspace state, not a destructive delete operation. High severity because misconfiguration of Drive settings by an AI agent could impact organizational notifications and workflow, affecting many users.

From the tool's definition Tool name 'configure_todrive_noemail' suggests configuration of Drive settings; context shows this MCP server manages Google Workspace administrative actions including Drive. The 'configure' prefix indicates modification of settings.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

configure_todrive_noemail Rate-limited

configure_todrive_noemail stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "configure_todrive_noemail": {
      "limits": [
        {
          "counter": "configure_todrive_noemail_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about configure_todrive_noemail

What does the configure_todrive_noemail tool do? +

configure_todrive_noemail. It is categorised as a Write tool in the GAM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on configure_todrive_noemail? +

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

What risk level is configure_todrive_noemail? +

configure_todrive_noemail is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit configure_todrive_noemail? +

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

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

configure_todrive_noemail is provided by the GAM MCP Server MCP server (ktibbs9417/gamcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.