users_filter_users_by_email
Filter Users by Email (requires an agency-level token, not a location PIT)
This record as markdown: /tools/aiwerk-mcp-server-ghl/users-filter-users-by-email.md
What users_filter_users_by_email does on Ghl
AI agents call users_filter_users_by_email to retrieve information from Ghl without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
skip | string | — | No of results to be skipped before returning the result |
limit | string | — | No of results to be limited before returning the result |
emails | string | Yes | Comma-separated list of email addresses to filter users |
deleted | boolean | — | Filter deleted users |
companyId | string | Yes | Company ID to filter users |
projection | string | — | Projection fields to return. Use "all" for all fields, or specify comma-separated field names. Default returns only id and email |
Parameters from the server's own tool schema.
Why users_filter_users_by_email is rated Low
Even though users_filter_users_by_email only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs users_filter_users_by_email safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ghl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For users_filter_users_by_email, this is the rule to start with:
users_filter_users_by_email 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 Ghl, apply this rule, and every users_filter_users_by_email call is checked against it from then on.
Questions about users_filter_users_by_email
Filter Users by Email (requires an agency-level token, not a location PIT). It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
users_filter_users_by_email accepts 6 parameters: skip, limit, emails, deleted, companyId, projection. Required: emails, companyId. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl MCP server in PolicyLayer and add a rule for users_filter_users_by_email: 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 Ghl. Nothing to install.
users_filter_users_by_email 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 users_filter_users_by_email 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 users_filter_users_by_email. 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.
users_filter_users_by_email is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ghl, and thousands of servers like it.
This server
Across the catalogue