list_reminders
AI agents call list_reminders to retrieve information from Apple Reminders MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or lists existing reminders without modifying data. It is a read-only operation with minimal blast radius—even if an AI misuses it, no data is created, deleted, or modified. Severity is low because the worst outcome is information disclosure of reminder contents, which poses minimal risk.
From the tool's definition Tool name 'list_reminders' and server description indicating it retrieves reminders across lists. Description is empty, but sibling tools (complete_reminder, create_reminder, delete_reminder, update_reminder) and server context confirm this is a query…
Attacks that exploit this kind of access
list_reminders. It is categorised as a Read tool in the Apple Reminders MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Apple Reminders MCP Server MCP server in PolicyLayer and add a rule for list_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 Apple Reminders MCP Server. Nothing to install.
list_reminders 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 list_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 list_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.
list_reminders is provided by the Apple Reminders MCP Server MCP server (pongsapakl/mcp-reminders). 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 →