# list_workspace_users

A read tool on the MCP Google Contacts Server MCP server.

Agent View of the PolicyLayer registry record for `list_workspace_users`. HTML page: https://policylayer.com/tools/4tal-mcp-google-contacts/list-workspace-users

## Facts

- Tool: `list_workspace_users`
- Server: MCP Google Contacts Server (`4tal/mcp-google-contacts`) — https://policylayer.com/tools/4tal-mcp-google-contacts.md
- Homepage: https://github.com/4tal/mcp-google-contacts
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "list_workspace_users",
    "arguments": {}
  }
}
```

## Why list_workspace_users is rated Low

The tool appears to list or query Workspace users from a directory, which is a read-only operation that retrieves information without side effects. Despite the empty description reducing confidence slightly, the naming convention and server context (which explicitly mentions 'accessing Google Workspace directories') strongly suggest this is a simple enumeration/query operation.

From the tool's own definition: "Tool name 'list_workspace_users' and server context (Google Workspace directory access) indicate data retrieval with no modification."

## Use case

AI agents call list_workspace_users 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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches MCP Google Contacts Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_workspace_users": {}
  }
}
```

## Other tools on MCP Google Contacts Server (18)

- `delete_contact` — Destructive — https://policylayer.com/tools/4tal-mcp-google-contacts/delete-contact.md
- `delete_contact_group` — Destructive — https://policylayer.com/tools/4tal-mcp-google-contacts/delete-contact-group.md
- `get_contact` — Read — https://policylayer.com/tools/4tal-mcp-google-contacts/get-contact.md
- `get_contact_group` — Read — https://policylayer.com/tools/4tal-mcp-google-contacts/get-contact-group.md
- `get_other_contacts` — Read — https://policylayer.com/tools/4tal-mcp-google-contacts/get-other-contacts.md
- `list_contact_groups` — Read — https://policylayer.com/tools/4tal-mcp-google-contacts/list-contact-groups.md
- `list_contacts` — Read — https://policylayer.com/tools/4tal-mcp-google-contacts/list-contacts.md
- `search_contacts` — Read — https://policylayer.com/tools/4tal-mcp-google-contacts/search-contacts.md
- `search_contacts_by_group` — Read — https://policylayer.com/tools/4tal-mcp-google-contacts/search-contacts-by-group.md
- `search_directory` — Read — https://policylayer.com/tools/4tal-mcp-google-contacts/search-directory.md
- `add_contacts_to_group` — Write — https://policylayer.com/tools/4tal-mcp-google-contacts/add-contacts-to-group.md
- `create_contact` — Write — https://policylayer.com/tools/4tal-mcp-google-contacts/create-contact.md
- `create_contact_advanced` — Write — https://policylayer.com/tools/4tal-mcp-google-contacts/create-contact-advanced.md
- `create_contact_group` — Write — https://policylayer.com/tools/4tal-mcp-google-contacts/create-contact-group.md
- `remove_contacts_from_group` — Write — https://policylayer.com/tools/4tal-mcp-google-contacts/remove-contacts-from-group.md
- `update_contact` — Write — https://policylayer.com/tools/4tal-mcp-google-contacts/update-contact.md
- `update_contact_advanced` — Write — https://policylayer.com/tools/4tal-mcp-google-contacts/update-contact-advanced.md
- `update_contact_group` — Write — https://policylayer.com/tools/4tal-mcp-google-contacts/update-contact-group.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=4tal-mcp-google-contacts · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/4tal-mcp-google-contacts