GOOGLESUPER_LIST_HISTORY

Tool to list Gmail mailbox change history since a known startHistoryId. Use when performing incremental mailbox syncs to fetch only new changes.

SERVERGoogle Super SOURCEgooglesuper

Low RISK CLASS

Category Read

Parameters 60 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/googlesuper/googlesuper-list-history.md

WHAT IT DOES

What GOOGLESUPER_LIST_HISTORY does on Google Super

AI agents call GOOGLESUPER_LIST_HISTORY 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 user's email address. Use 'me' to specify the authenticated user.
`label_id`	string	—	Only return history records involving messages with this label ID.
`page_token`	string	—	Token to retrieve a specific page of results.
`max_results`	integer	—	Maximum number of history records to return. Default is 100; max is 500.
`history_types`	array	—	Filter by specific history types. Allowed values: messageAdded, messageDeleted, labelAdded, labelRemoved.
`start_history_id`	string	—	Required. Returns history records after this ID. If the ID is invalid or too old, the API returns 404. Perform a full sync in that case.

Parameters from the server's own tool schema.

RISK

Why GOOGLESUPER_LIST_HISTORY is rated Low

This tool retrieves historical change data from Gmail without modifying, creating, or deleting any messages or data. It is a query/list operation that accesses Gmail metadata and change records.

From the tool's definition Tool description explicitly states it 'list[s]' and 'fetch[es]' change history from Gmail mailbox; performs 'incremental mailbox syncs' to retrieve 'only new changes' — all read-only retrieval operations with no modification or deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs GOOGLESUPER_LIST_HISTORY 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_LIST_HISTORY, this is the rule to start with:

GOOGLESUPER_LIST_HISTORY Allowed

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

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

The button opens the PolicyLayer dashboard: create your workspace, connect Google Super, apply this rule, and every GOOGLESUPER_LIST_HISTORY call is checked against it from then on.

FAQ

Questions about GOOGLESUPER_LIST_HISTORY

What does the GOOGLESUPER_LIST_HISTORY tool do? +

Tool to list Gmail mailbox change history since a known startHistoryId. Use when performing incremental mailbox syncs to fetch only new changes. It is categorised as a Read tool in the Google Super MCP Server, which means it retrieves data without modifying state.

What parameters does GOOGLESUPER_LIST_HISTORY accept? +

GOOGLESUPER_LIST_HISTORY accepts 6 parameters: user_id, label_id, page_token, max_results, history_types, start_history_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on GOOGLESUPER_LIST_HISTORY? +

Register the Google Super MCP server in PolicyLayer and add a rule for GOOGLESUPER_LIST_HISTORY: 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.

What risk level is GOOGLESUPER_LIST_HISTORY? +

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

Can I rate-limit GOOGLESUPER_LIST_HISTORY? +

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

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

GOOGLESUPER_LIST_HISTORY 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.

KEEP EXPLORING

More on Google Super, and thousands of servers like it.

This server

All 200 Google Super tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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