claudecron_add_task
AI agents use claudecron_add_task to create or update resources in Email MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Email MCP Server environment.
The 'add_task' operation creates a new task resource without irreversibly destroying data. This is a Write operation. Severity is medium because task creation in an email/communication context could trigger unintended emails or schedule unintended actions if misused by an agent, but the operation is reversible (tasks can be deleted).
From the tool's definition Tool name 'claudecron_add_task' indicates creation of a task resource. The parent server description mentions it enables users to 'send emails' and manage communications across multiple accounts, suggesting write-capable operations.
Attacks that exploit this kind of access
claudecron_add_task. It is categorised as a Write tool in the Email MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Email MCP Server MCP server in PolicyLayer and add a rule for claudecron_add_task: 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_add_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the claudecron_add_task 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_add_task. 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_add_task 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 →