Sets the default S/MIME config for the specified send-as alias
AI agents use set_default_smime_info 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 creates or modifies S/MIME configuration for email sending aliases. While it affects security-sensitive email settings, it does not delete data (not Destructive), execute arbitrary code (not Execute), or move money (not Financial). It is a Write operation because configuration changes are reversible.
From the tool's definition 'Sets the default S/MIME config' — modifies configuration settings for a send-as alias, which is reversible (can be updated or reconfigured later).
Attacks that exploit this kind of access
Sets the default S/MIME config for the specified send-as alias. 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 set_default_smime_info: 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.
set_default_smime_info 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 set_default_smime_info 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 set_default_smime_info. 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.
set_default_smime_info 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 →