Unified view of every upcoming date in the next N days: birthdays, maintenance due, warranties expiring, medication refills, subscription renewals, trips, provider visits, and follow-ups owed.
AI agents call upcoming_dates to retrieve information from Personal Brain without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves personal calendar and reminder data without modifying, deleting, or executing any actions. It is purely informational/retrieval in nature. While it exposes personal information (health, financial subscriptions, travel plans), the risk is low because the tool itself cannot modify data or trigger external actions—it only displays information that would help an AI agent stay informed.
From the tool's definition The tool provides a 'unified view' of upcoming dates and retrieves information about birthdays, maintenance, warranties, medication refills, subscriptions, trips, and appointments. These are all read operations with no modification or deletion of data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Unified view of every upcoming date in the next N days: birthdays, maintenance due, warranties expiring, medication refills, subscription renewals, trips, provider visits, and follow-ups owed. It is categorised as a Read tool in the Personal Brain MCP Server, which means it retrieves data without modifying state.
Register the Personal Brain MCP server in PolicyLayer and add a rule for upcoming_dates: 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 Personal Brain. Nothing to install.
upcoming_dates 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 upcoming_dates 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 upcoming_dates. 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.
upcoming_dates is provided by the Personal Brain MCP server (phantomts/personal-brain-mcp). 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 →