Create a new reminder/task
AI agents use create_reminder to create or update resources in MCP Calendar Assistant — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Calendar Assistant environment.
This tool creates new reminder/task data, which is a reversible write operation. Reminders can be edited, deleted, or dismissed without permanent consequences. The blast radius is minimal—misuse would result in unwanted reminders cluttering a calendar, not financial loss or data destruction. Severity is low because the impact is easily remediated by the user deleting or dismissing unwanted reminders.
From the tool's definition Tool name 'create_reminder' and description 'Create a new reminder/task' indicate data creation without irreversible deletion or financial impact.
Attacks that exploit this kind of access
Create a new reminder/task. It is categorised as a Write tool in the MCP Calendar Assistant MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Calendar Assistant MCP server in PolicyLayer and add a rule for create_reminder: 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 Calendar Assistant. Nothing to install.
create_reminder 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 create_reminder 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 create_reminder. 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.
create_reminder is provided by the MCP Calendar Assistant MCP server (momer17/mailmcp). 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 →