GOOGLESUPER_FETCH_MESSAGE_BY_THREAD_ID
Retrieves messages from a Gmail thread using its thread_id, where the thread must be accessible by the specified user_id.
This record as markdown: /tools/googlesuper/googlesuper-fetch-message-by-thread-id.md
What GOOGLESUPER_FETCH_MESSAGE_BY_THREAD_ID does on Google Super
AI agents call GOOGLESUPER_FETCH_MESSAGE_BY_THREAD_ID to retrieve information from Google Super without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
user_id | string | — | The email address of the user. |
thread_id | string | — | Unique ID of the thread, obtainable from actions like 'listThreads' or 'fetchEmails'. |
page_token | string | — | Opaque page token for fetching a specific page of messages if results are paginated. |
Parameters from the server's own tool schema.
Why GOOGLESUPER_FETCH_MESSAGE_BY_THREAD_ID is rated Low
This tool performs a read-only operation that queries and retrieves existing Gmail messages. It has no side effects—it does not create, modify, delete, or execute any operations. The access control (user_id requirement) is a standard permission check. Blast radius is minimal as misuse would only expose data the user already has access to.
From the tool's definition Tool name contains 'FETCH_MESSAGE' and description states 'Retrieves messages from a Gmail thread' with no modification, deletion, or execution capabilities mentioned.
Attacks that exploit this kind of access
The rule that runs GOOGLESUPER_FETCH_MESSAGE_BY_THREAD_ID safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Super, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For GOOGLESUPER_FETCH_MESSAGE_BY_THREAD_ID, this is the rule to start with:
GOOGLESUPER_FETCH_MESSAGE_BY_THREAD_ID is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Google Super, apply this rule, and every GOOGLESUPER_FETCH_MESSAGE_BY_THREAD_ID call is checked against it from then on.
Questions about GOOGLESUPER_FETCH_MESSAGE_BY_THREAD_ID
Retrieves messages from a Gmail thread using its thread_id, where the thread must be accessible by the specified user_id. It is categorised as a Read tool in the Google Super MCP Server, which means it retrieves data without modifying state.
GOOGLESUPER_FETCH_MESSAGE_BY_THREAD_ID accepts 3 parameters: user_id, thread_id, page_token. The full parameter table on this page comes from the server's own tool schema.
Register the Google Super MCP server in PolicyLayer and add a rule for GOOGLESUPER_FETCH_MESSAGE_BY_THREAD_ID: 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 Super. Nothing to install.
GOOGLESUPER_FETCH_MESSAGE_BY_THREAD_ID 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 GOOGLESUPER_FETCH_MESSAGE_BY_THREAD_ID 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 GOOGLESUPER_FETCH_MESSAGE_BY_THREAD_ID. 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.
GOOGLESUPER_FETCH_MESSAGE_BY_THREAD_ID is provided by the Google Super MCP server (googlesuper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Super, and thousands of servers like it.
This server
Across the catalogue