Returns per-account sync state, last sync time, total cached emails.
AI agents call sync_status to retrieve information from MCP Email Service without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only diagnostic tool that retrieves system metadata about email synchronization status. It has no side effects, does not modify or delete data, and does not execute operations. It poses minimal security risk if misused by an AI agent, as an attacker would only gain visibility into sync metadata already stored locally.
From the tool's definition Tool returns sync state, last sync time, and total cached emails—purely informational queries with no modification, deletion, or execution capability. Described as 'Returns' per-account data.
Documented attack patterns abuse exactly the kind of access sync_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Email Service, and nothing reaches the server without passing your rules. This is the rule we recommend for sync_status:
{
"version": "1",
"default": "deny",
"tools": {
"sync_status": {}
}
}sync_status 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.
Returns per-account sync state, last sync time, total cached emails. It is categorised as a Read tool in the MCP Email Service MCP Server, which means it retrieves data without modifying state.
Register the MCP Email Service MCP server in PolicyLayer and add a rule for sync_status: 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 MCP Email Service. Nothing to install.
sync_status 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 sync_status 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 sync_status. 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.
sync_status is provided by the MCP Email Service MCP server (leeguooooo/mailbox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Email Service, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 MCP Email Service tools catalogued and risk-classified — across an index of 43,000+ MCP servers.