Search Google Contacts.
AI agents call contacts_search to retrieve information from AIOS Co-Founder MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries Google Contacts data without creating, modifying, deleting, or executing any operations. It is purely informational retrieval, matching the 'Read' category definition. Severity is low because searching contacts carries minimal risk—it does not expose sensitive data irreversibly, perform external actions, or cause financial impact.
From the tool's definition Tool name is 'contacts_search' and description states 'Search Google Contacts.' The verb 'search' and lack of any modification language indicate this is a retrieval-only operation with no side effects.
Attacks that exploit this kind of access
Search Google Contacts. It is categorised as a Read tool in the AIOS Co-Founder MCP MCP Server, which means it retrieves data without modifying state.
Register the AIOS Co-Founder MCP server in PolicyLayer and add a rule for contacts_search: 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 AIOS Co-Founder MCP. Nothing to install.
contacts_search 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 contacts_search 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 contacts_search. 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.
contacts_search is provided by the AIOS Co-Founder MCP server (varun-b-nagaraj/python-mcp-server). 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 →