Anniversaries and important repeating dates beyond birthdays (wedding, met, deaths, milestones).
AI agents call anniversaries 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 stored anniversary and milestone dates from a personal database. It is purely informational with no side effects—no data is created, modified, deleted, or executed. The blast radius of misuse is minimal; an AI agent retrieving anniversary dates poses no security, financial, or operational risk.
From the tool's definition Tool name 'anniversaries' and description indicating it retrieves 'important repeating dates' (wedding, met, deaths, milestones) with no mention of creation, modification, or deletion capabilities.
Attacks that exploit this kind of access
Anniversaries and important repeating dates beyond birthdays (wedding, met, deaths, milestones). 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 anniversaries: 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.
anniversaries 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 anniversaries 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 anniversaries. 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.
anniversaries 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 →