New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

search_contacts

A read tool on the MCP Google Contacts MCP server.

SERVERMCP Google Contacts Server SOURCE4tal/mcp-google-contacts
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/4tal-mcp-google-contacts/search-contacts.md

What search_contacts does on MCP Google Contacts Server

AI agents call search_contacts to retrieve information from MCP Google Contacts Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why search_contacts is rated Low

Search operations retrieve and filter existing data without creating, modifying, or deleting records. This follows the Read category pattern of querying data with no side effects. The sibling tools include clearly destructive (delete_*) and write operations (create_*, add_*), which contextually confirm this tool performs read-only operations.

From the tool's definition Tool name 'search_contacts' indicates a query/retrieval operation. Server description mentions 'searching' contacts as part of comprehensive management.

Questions about search_contacts

What does the search_contacts tool do? +

search_contacts is a read tool on the MCP Google Contacts Server MCP server. It is categorised as a Read tool in the MCP Google Contacts Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_contacts? +

Register the MCP Google Contacts Server MCP server in PolicyLayer and add a rule for search_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 Contacts Server. Nothing to install.

What risk level is search_contacts? +

search_contacts is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_contacts? +

Yes. Add a rate_limit block to the search_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.

How do I block search_contacts completely? +

Set action: deny in the PolicyLayer policy for search_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.

What MCP server provides search_contacts? +

search_contacts is provided by the MCP Google Contacts Server MCP server (4tal/mcp-google-contacts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on MCP Google Contacts Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of MCP Google Contacts Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.