Filter/look up users by email address within a location
AI agents call filter_users_by_email to retrieve information from GoHighLevel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves or queries user data based on an email filter criterion. It performs a lookup operation that does not create, modify, delete, or execute any external actions. This is a classic Read category tool with minimal security risk even if misused by an AI agent.
From the tool's definition Tool description states 'Filter/look up users by email address within a location' — this is a query/search operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access filter_users_by_email gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GoHighLevel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for filter_users_by_email:
{
"version": "1",
"default": "deny",
"tools": {
"filter_users_by_email": {}
}
}filter_users_by_email is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Filter/look up users by email address within a location. 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 (busybee3333/go-high-level-mcp-2026-complete). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 566 GoHighLevel MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
566 GoHighLevel MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.