google-workspace.contacts_search

Search the user

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

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/cowork-os/google-workspace.contacts-search.md

WHAT IT DOES

What google-workspace.contacts_search does on CoWork OS

AI agents call google-workspace.contacts_search to retrieve information from CoWork OS without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why google-workspace.contacts_search is rated Low

Tool retrieves contact search results without modifying data or side effects.

From the tool's definition Search the user

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs google-workspace.contacts_search safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For google-workspace.contacts_search, this is the rule to start with:

google-workspace.contacts_search Allowed

google-workspace.contacts_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "google-workspace.contacts_search": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every google-workspace.contacts_search call is checked against it from then on.

FAQ

Questions about google-workspace.contacts_search

What does the google-workspace.contacts_search tool do? +

Search the user. It is categorised as a Read tool in the CoWork OS MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on google-workspace.contacts_search? +

Register the CoWork OS MCP server in PolicyLayer and add a rule for google-workspace.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 CoWork OS. Nothing to install.

What risk level is google-workspace.contacts_search? +

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

Can I rate-limit google-workspace.contacts_search? +

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

How do I block google-workspace.contacts_search completely? +

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

What MCP server provides google-workspace.contacts_search? +

google-workspace.contacts_search is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 354 CoWork OS tools →

Across the catalogue

binary_search on 010 Editor →evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →