claudecron_get_history
AI agents call claudecron_get_history to retrieve information from Email MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name pattern 'get_history' indicates a retrieval operation with no side effects. Given the server's primary function of reading and managing emails, this tool likely queries past events or email history. However, confidence is moderated (0.7) due to empty description and uncertainty about what 'claudecron' context implies.
From the tool's definition Tool name 'claudecron_get_history' suggests retrieval of historical data; server description emphasizes read/search capabilities ('read, search, and send emails'); no description provided for this specific tool.
Attacks that exploit this kind of access
claudecron_get_history. It is categorised as a Read tool in the Email MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Email MCP Server MCP server in PolicyLayer and add a rule for claudecron_get_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 Email MCP Server. Nothing to install.
claudecron_get_history 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 claudecron_get_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.
Set action: deny in the PolicyLayer policy for claudecron_get_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.
claudecron_get_history is provided by the Email MCP Server MCP server (sventern/mcp_email). 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 →