Upcoming birthdays from Google Contacts birthday field. Requires People API integration.
AI agents call upcoming_birthdays 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 tool retrieves and displays birthday information from an existing data source (Google Contacts). It performs no data creation, modification, deletion, or external triggering. The operation is read-only with minimal blast radius—incorrect output would only affect calendar or reminder accuracy, not cause financial harm, destructive changes, or code execution.
From the tool's definition Tool description states it retrieves 'Upcoming birthdays from Google Contacts birthday field' — a query operation that reads contact data without modification or side effects.
Attacks that exploit this kind of access
Upcoming birthdays from Google Contacts birthday field. Requires People API integration. 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 upcoming_birthdays: 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.
upcoming_birthdays 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_birthdays 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_birthdays. 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_birthdays 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 →