Full contact record by resourceName (e.g. 'people/c1234567890123').
AI agents call get_contact_details 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 contact information by a resource identifier. It performs a query operation with no side effects—it does not create, modify, delete, or execute operations. The blast radius of misuse is minimal: an attacker could learn contact details but cannot alter data, execute code, or cause financial harm. Severity is low because contact enumeration is a common read operation in personal assistant contexts.
From the tool's definition Tool name 'get_contact_details' and description 'Full contact record by resourceName' indicates retrieval of existing contact data with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Full contact record by resourceName (e.g. 'people/c1234567890123'). 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 get_contact_details: 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.
get_contact_details 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 get_contact_details 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 get_contact_details. 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.
get_contact_details 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 →