filter-users-by-email
Filter users by company ID, deleted status, and email array
This record as markdown: /tools/drausal-gohighlevel-mcp/filter-users-by-email.md
What filter-users-by-email does on GoHighLevel MCP Server
AI agents call filter-users-by-email to retrieve information from GoHighLevel MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why filter-users-by-email is rated Low
This tool performs a read-only query operation that filters and retrieves user information. It accepts filter parameters (company ID, deleted status, email array) and returns matching results. No data is created, modified, deleted, or executed—it is a pure retrieval operation with no side effects on the system state.
From the tool's definition Tool name 'filter-users-by-email' and description 'Filter users by company ID, deleted status, and email array' indicate a query/search operation that retrieves user data based on filter criteria without modifying or deleting anything.
Attacks that exploit this kind of access
The rule that runs filter-users-by-email safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GoHighLevel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For filter-users-by-email, this is the rule to start with:
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 GoHighLevel MCP Server, apply this rule, and every filter-users-by-email call is checked against it from then on.
Questions about filter-users-by-email
Filter users by company ID, deleted status, and email array. It is categorised as a Read tool in the GoHighLevel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for 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 GoHighLevel MCP Server. Nothing to install.
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 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 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.
filter-users-by-email is provided by the GoHighLevel MCP Server MCP server (drausal/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GoHighLevel MCP Server, and thousands of servers like it.
This server
Across the catalogue