Updates language settings
AI agents use update_language to create or update resources in Gmail MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gmail MCP Server environment.
This tool modifies (rather than deletes) account settings, making it a Write action. The blast radius is low since language preference changes are reversible, non-destructive, and do not affect email data or enable further unauthorized access. No financial, data deletion, or code execution implications.
From the tool's definition Tool name 'update_language' and description 'Updates language settings' indicate modification of user account configuration settings. The context of Gmail MCP server confirms this operates on Gmail account settings through OAuth2 authentication.
Attacks that exploit this kind of access
Updates language settings. It is categorised as a Write tool in the Gmail MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gmail MCP Server MCP server in PolicyLayer and add a rule for update_language: 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 Gmail MCP Server. Nothing to install.
update_language 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 update_language 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 update_language. 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.
update_language is provided by the Gmail MCP Server MCP server (nk900600/gmail-mcp). 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 →