Lists S/MIME configs for the specified send-as alias
AI agents call list_smime_info to retrieve information from Gmail MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves S/MIME (Secure/Multipurpose Internet Mail Extensions) configuration information for a send-as alias. It performs a data retrieval operation without creating, modifying, deleting, or executing any actions. The blast radius if misused by an agent is minimal—it can only expose existing cryptographic configuration metadata, not alter security settings or compromise messages.
From the tool's definition Tool name 'list_smime_info' and description 'Lists S/MIME configs' indicate a retrieval operation with no mutation or side effects. The verb 'list' explicitly denotes a read operation.
Attacks that exploit this kind of access
Lists S/MIME configs for the specified send-as alias. It is categorised as a Read tool in the Gmail MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Gmail MCP Server MCP server in PolicyLayer and add a rule for list_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.
list_smime_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_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 list_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.
list_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 →