Get statistics about configured email accounts.
AI agents call get_account_stats to retrieve information from MCP Email Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves statistical information about email accounts (counts, sizes, dates, etc.) without side effects. It performs a read-only query that does not create, modify, delete, or execute any operations.
From the tool's definition Tool name 'get_account_stats' and description 'Get statistics about configured email accounts' indicate retrieval of metadata/statistics with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get statistics about configured email accounts. It is categorised as a Read tool in the MCP Email Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Email Server MCP server in PolicyLayer and add a rule for get_account_stats: 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 Server. Nothing to install.
get_account_stats 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_account_stats 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_account_stats. 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_account_stats is provided by the MCP Email Server MCP server (kentaroh7777/mcp-email-server). 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 →