openid_connect_user_info

Get the identity of a user who authorized Sign in with Slack.

SERVERSlack SOURCEkarbassi/slack-mcp

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/karbassi-slack-mcp/openid-connect-user-info.md

WHAT IT DOES

What openid_connect_user_info does on Slack

AI agents call openid_connect_user_info to retrieve information from Slack without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why openid_connect_user_info is rated Low

This tool retrieves identity information about a user via OpenID Connect. It is a read-only operation that fetches user profile/identity data. The severity is medium because it exposes personal identity information (PII) which could be misused for social engineering or account enumeration, but it does not modify any data.

From the tool's definition "Get the identity of a user who authorized Sign in with Slack"

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs openid_connect_user_info safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Slack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For openid_connect_user_info, this is the rule to start with:

openid_connect_user_info Allowed

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

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

The button opens the PolicyLayer dashboard: create your workspace, connect Slack, apply this rule, and every openid_connect_user_info call is checked against it from then on.

FAQ

Questions about openid_connect_user_info

What does the openid_connect_user_info tool do? +

Get the identity of a user who authorized Sign in with Slack. It is categorised as a Read tool in the Slack MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on openid_connect_user_info? +

Register the Slack MCP server in PolicyLayer and add a rule for openid_connect_user_info: 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 Slack. Nothing to install.

What risk level is openid_connect_user_info? +

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

Can I rate-limit openid_connect_user_info? +

Yes. Add a rate_limit block to the openid_connect_user_info 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 openid_connect_user_info completely? +

Set action: deny in the PolicyLayer policy for openid_connect_user_info. 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 openid_connect_user_info? +

openid_connect_user_info is provided by the Slack MCP server (karbassi/slack-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Slack, and thousands of servers like it.

This server

All 233 Slack tools →

Across the catalogue

The MCP Attack Database →

Guides

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