Get changes within a previous search query since its last queryState. You MUST pass the same filter parameters as the original search_emails call. Returns added and removed email IDs relative to that search.
AI agents call get_search_updates to retrieve information from JMAP MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries changes to a previous search result set and returns email IDs that have been added or removed from the matching set. It is a read-only operation that retrieves data about changes in search results since a prior state. It does not modify, delete, execute code, or perform financial operations.
From the tool's definition Tool name 'get_search_updates' and description stating it 'Returns added and removed email IDs relative to that search' indicates retrieval of query results without modification. No deletion, creation, execution, or financial operations are performed.
Documented attack patterns abuse exactly the kind of access get_search_updates gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and JMAP MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_search_updates:
{
"version": "1",
"default": "deny",
"tools": {
"get_search_updates": {}
}
}get_search_updates is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get changes within a previous search query since its last queryState. You MUST pass the same filter parameters as the original search_emails call. Returns added and removed email IDs relative to that search. It is categorised as a Read tool in the JMAP MCP MCP Server, which means it retrieves data without modifying state.
Register the JMAP MCP server in PolicyLayer and add a rule for get_search_updates: 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 JMAP MCP. Nothing to install.
get_search_updates 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 get_search_updates 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 get_search_updates. 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.
get_search_updates is provided by the JMAP MCP server (wyattjoh/jmap-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 JMAP MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
11 JMAP MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.