list-contacts
List Google Contacts. Returns: array with resourceName, names, emailAddresses, phoneNumbers per contact. Use when: viewing contact list, searching by name. Note: use personFields to limit data.
This record as markdown: /tools/199-biotechnologies-mcp-google/list-contacts.md
What list-contacts does on MCP Google Workspace
AI agents call list-contacts to retrieve information from MCP Google Workspace without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list-contacts is rated Low
This tool retrieves contact data without creating, modifying, or deleting entries. It is a straightforward query operation that returns structured contact information. While contacts may contain sensitive PII (names, emails, phone numbers), the tool itself performs only read access, making it a Read category risk.
From the tool's definition Tool name 'list-contacts' and description states it 'List[s] Google Contacts' and 'Returns: array with resourceName, names, emailAddresses, phoneNumbers per contact.' The use cases are 'viewing contact list, searching by name,' which are retrieval operations…
Attacks that exploit this kind of access
The rule that runs list-contacts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Google Workspace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list-contacts, this is the rule to start with:
list-contacts is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP Google Workspace, apply this rule, and every list-contacts call is checked against it from then on.
Questions about list-contacts
List Google Contacts. Returns: array with resourceName, names, emailAddresses, phoneNumbers per contact. Use when: viewing contact list, searching by name. Note: use personFields to limit data. It is categorised as a Read tool in the MCP Google Workspace MCP Server, which means it retrieves data without modifying state.
Register the MCP Google Workspace MCP server in PolicyLayer and add a rule for list-contacts: 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 MCP Google Workspace. Nothing to install.
list-contacts 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 list-contacts 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 list-contacts. 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.
list-contacts is provided by the MCP Google Workspace MCP server (199-mcp/mcp-google). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Google Workspace, and thousands of servers like it.
This server
Across the catalogue