Contacts with birthdays in the next N days (Google People birthday field).
AI agents call birthday_reminders to retrieve information from Nexus Core without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward data retrieval tool that queries contact birthday information. It has no side effects, does not modify data, execute code, delete records, or move money. The blast radius of misuse is minimal—an AI agent could only retrieve birthday data it likely already has permission to access through the connected Google account.
From the tool's definition Tool retrieves birthday information from Google People API ('Contacts with birthdays in the next N days'). The description indicates a query/fetch operation with no modification, deletion, or external triggering.
Attacks that exploit this kind of access
Contacts with birthdays in the next N days (Google People birthday field). It is categorised as a Read tool in the Nexus Core MCP Server, which means it retrieves data without modifying state.
Register the Nexus Core MCP server in PolicyLayer and add a rule for birthday_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 Nexus Core. Nothing to install.
birthday_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 birthday_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 birthday_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.
birthday_reminders is provided by the Nexus Core MCP server (noumenon-ai/nexus-core). 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 →