filter_users_by_email

Filter/look up users by email address within a location

SERVERGoHighLevel MCP Server SOURCEbusybee3333/go-high-level-mcp-2026-complete

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/busybee3333-go-high-level-mcp-2026-complete/filter-users-by-email.md

WHAT IT DOES

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.

RISK

Why filter_users_by_email is rated Low

This tool retrieves or searches for user records based on email criteria. It is a lookup function that queries existing data without side effects, making it a Read operation. The severity is low because retrieving user contact information via email filter poses minimal risk even if misused by an AI agent — it does not modify data, execute code, trigger financial transactions, or delete information.

From the tool's definition Tool name is 'filter_users_by_email' and description states 'Filter/look up users by email address within a location' — these are query/retrieval operations with no modification, deletion, or execution of external operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Allowed

filter_users_by_email 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": {
    "filter_users_by_email": {}
  }
}

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

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.

FAQ

Questions about filter_users_by_email

What does the filter_users_by_email tool do? +

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.

How do I enforce a policy on filter_users_by_email? +

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.

What risk level is filter_users_by_email? +

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

Can I rate-limit filter_users_by_email? +

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.

How do I block filter_users_by_email completely? +

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.

What MCP server provides filter_users_by_email? +

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.

KEEP EXPLORING

More on GoHighLevel MCP Server, and thousands of servers like it.

This server

All 566 GoHighLevel MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

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