Get detailed profile information for a specific user
AI agents call slack_get_user_profile to retrieve information from Helm Chart CLI without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves user profile information from Slack without creating, modifying, or deleting any data. It is a read-only operation with minimal blast radius if misused—an AI agent could retrieve profile data about users but cannot perform unauthorized actions beyond accessing information that may already be visible or accessible within Slack's normal permission model.
From the tool's definition Tool name 'slack_get_user_profile' and description 'Get detailed profile information for a specific user' indicate retrieval of user data with no modification or side effects.
Attacks that exploit this kind of access
Get detailed profile information for a specific user. It is categorised as a Read tool in the Helm Chart CLI MCP Server, which means it retrieves data without modifying state.
Register the Helm Chart CLI MCP server in PolicyLayer and add a rule for slack_get_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 Helm Chart CLI. Nothing to install.
slack_get_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 slack_get_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 slack_get_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.
slack_get_user_profile is provided by the Helm Chart CLI MCP server (jeff-nasseri/servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →