get_slack_user_profile
Get detailed profile for a specific Slack user. Get user ID from list_slack_users or from a message, or use @username format.
This record as markdown: /tools/freshdesk/get-slack-user-profile.md
What get_slack_user_profile does on Freshdesk
AI agents call get_slack_user_profile 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 get_slack_user_profile is rated Low
This tool retrieves user profile information from Slack without side effects. It is a read-only query operation that fetches and returns existing data. The blast radius is minimal since it only accesses profile metadata and does not modify, delete, or execute any operations.
From the tool's definition Tool name 'get_slack_user_profile' and description 'Get detailed profile for a specific Slack user' indicate retrieval of user profile data with no modification, deletion, or execution.
Attacks that exploit this kind of access
The rule that runs get_slack_user_profile 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 get_slack_user_profile, this is the rule to start with:
get_slack_user_profile 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 get_slack_user_profile call is checked against it from then on.
Questions about get_slack_user_profile
Get detailed profile for a specific Slack user. Get user ID from list_slack_users or from a message, or use @username format. 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 get_slack_user_profile: 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.
get_slack_user_profile 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 get_slack_user_profile 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 get_slack_user_profile. 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.
get_slack_user_profile 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