add_to_reminders
AI agents use add_to_reminders to create or update resources in Meducate MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meducate MCP environment.
The tool creates new reminder entries, which is reversible and has no destructive side effects. While the description is empty (lowering confidence slightly), the name clearly indicates data modification rather than retrieval, execution, or deletion.
From the tool's definition Tool name 'add_to_reminders' indicates creating or modifying reminder data. The action suggests reversible data creation (adding entries to a reminders list), consistent with Write category behavior.
Attacks that exploit this kind of access
add_to_reminders. It is categorised as a Write tool in the Meducate MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Meducate MCP server in PolicyLayer and add a rule for add_to_reminders: 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 Meducate MCP. Nothing to install.
add_to_reminders 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 add_to_reminders 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 add_to_reminders. 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.
add_to_reminders is provided by the Meducate MCP server (joshnuku/meducate-mcp-demo). 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 →