AI agents call slack_get_user_profile to retrieve information from Mcp Gmail without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description, the tool name clearly indicates a retrieval operation ('get_user_profile'). This fetches user profile data without side effects. The low severity reflects minimal blast radius—exposing profile information is less risky than write, execute, or destructive operations. Confidence is 0.7 due to the empty description not confirming intent, but the name is a strong indicator.
From the tool's definition Tool name 'slack_get_user_profile' indicates retrieval of user profile information with no modification. The description is empty, which slightly lowers confidence, but the naming pattern is unambiguous: 'get' operations are Read operations.
Attacks that exploit this kind of access
slack_get_user_profile. It is categorised as a Read tool in the Mcp Gmail MCP Server, which means it retrieves data without modifying state.
Register the Mcp Gmail 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 Mcp Gmail. 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 Mcp Gmail MCP server (@monsoft/mcp-gmail). 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 →