This record as markdown: /tools/karbassi-slack-mcp/team-profile-get.md
What team_profile_get does on Slack
AI agents call team_profile_get 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.
Why team_profile_get is rated Low
This tool retrieves metadata about a Slack team/workspace profile. It performs a query-only operation that reads data without creating, modifying, deleting, or executing external actions. The blast radius is minimal since it only exposes existing team profile information that workspace members can typically access through normal Slack UI.
From the tool's definition Tool name 'team_profile_get' and description 'Retrieve a team's profile' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs team_profile_get 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 team_profile_get, this is the rule to start with:
team_profile_get 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 Slack, apply this rule, and every team_profile_get call is checked against it from then on.
Questions about team_profile_get
Retrieve a team's profile. It is categorised as a Read tool in the Slack MCP Server, which means it retrieves data without modifying state.
Register the Slack MCP server in PolicyLayer and add a rule for team_profile_get: 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.
team_profile_get 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 team_profile_get 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 team_profile_get. 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.
team_profile_get 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.
More on Slack, and thousands of servers like it.
This server
Across the catalogue