lookup_user_by_email
Find a Slack user by their email address. PREFERRED method for resolving users — exact match, no ambiguity. WHEN TO USE: Always use this tool (instead of list_slack_users name search) when you have the user
This record as markdown: /tools/freshdesk/lookup-user-by-email.md
What lookup_user_by_email does on Freshdesk
AI agents call lookup_user_by_email to retrieve information from Freshdesk without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why lookup_user_by_email is rated Low
This is a straightforward query/search operation that retrieves user information based on an email address. It has no side effects, does not modify data, execute code, or affect system state. The exact-match lookup minimizes risk of unintended consequences compared to a broader search.
From the tool's definition Tool performs a 'lookup' operation to 'find a Slack user by their email address' with 'exact match' semantics. No modification, deletion, or execution is described. The description emphasizes it as the PREFERRED method for resolving/searching users.
Attacks that exploit this kind of access
The rule that runs lookup_user_by_email safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freshdesk, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For lookup_user_by_email, this is the rule to start with:
lookup_user_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 Freshdesk, apply this rule, and every lookup_user_by_email call is checked against it from then on.
Questions about lookup_user_by_email
Find a Slack user by their email address. PREFERRED method for resolving users — exact match, no ambiguity. WHEN TO USE: Always use this tool (instead of list_slack_users name search) when you have the user. It is categorised as a Read tool in the Freshdesk MCP Server, which means it retrieves data without modifying state.
Register the Freshdesk MCP server in PolicyLayer and add a rule for lookup_user_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 Freshdesk. Nothing to install.
lookup_user_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 lookup_user_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 lookup_user_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.
lookup_user_by_email is provided by the Freshdesk MCP server (@mindstone-engineering/mcp-server-freshdesk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freshdesk, and thousands of servers like it.
This server
Across the catalogue