gmail_users_settings_getImap

Get IMAP settings

SERVERGoogle Workspace Gmail (gws CLI) SOURCE@gws mcp -s gmail

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/google-workspace-gmail/gmail-users-settings-getimap.md

WHAT IT DOES

What gmail_users_settings_getImap does on Google Workspace Gmail (gws CLI)

AI agents call gmail_users_settings_getImap to retrieve information from Google Workspace Gmail (gws CLI) without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why gmail_users_settings_getImap is rated Low

This tool retrieves IMAP configuration settings for a Gmail account. It performs a read-only query of settings data without creating, modifying, deleting, or executing any actions. While IMAP settings could theoretically be sensitive (e.g., revealing enabled/disabled status), the action itself is passive data retrieval.

From the tool's definition Tool name contains 'get' and description states 'Get IMAP settings', indicating a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gmail_users_settings_getImap safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Google Workspace Gmail (gws CLI), and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gmail_users_settings_getImap, this is the rule to start with:

gmail_users_settings_getImap Allowed

gmail_users_settings_getImap 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": {
    "gmail_users_settings_getImap": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Google Workspace Gmail (gws CLI), apply this rule, and every gmail_users_settings_getImap call is checked against it from then on.

FAQ

Questions about gmail_users_settings_getImap

What does the gmail_users_settings_getImap tool do? +

Get IMAP settings. It is categorised as a Read tool in the Google Workspace Gmail (gws CLI) MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on gmail_users_settings_getImap? +

Register the Google Workspace Gmail (gws CLI) MCP server in PolicyLayer and add a rule for gmail_users_settings_getImap: 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 Gmail (gws CLI). Nothing to install.

What risk level is gmail_users_settings_getImap? +

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

Can I rate-limit gmail_users_settings_getImap? +

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

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

gmail_users_settings_getImap is provided by the Google Workspace Gmail (gws CLI) MCP server (@gws mcp -s gmail). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Google Workspace Gmail (gws CLI), and thousands of servers like it.

This server

All 79 Google Workspace Gmail (gws CLI) tools →

Across the catalogue

The MCP Attack Database →

Guides

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