Resolve a channel name to its ID.
AI agents call slack_find_channel to retrieve information from Work Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple name resolution (lookup) with no side effects, no data modification, and no external actions triggered. It falls squarely into the Read category as a retrieval/query function. Severity is low because exposing channel IDs carries minimal risk in a Slack workspace context — this information is typically discoverable through normal Slack usage.
From the tool's definition Tool description states 'Resolve a channel name to its ID' — a lookup operation that retrieves identifiers without modifying data. The verb 'resolve' and the read-only nature of name-to-ID translation confirm this is a query operation.
Attacks that exploit this kind of access
Resolve a channel name to its ID. It is categorised as a Read tool in the Work Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Work Integrations MCP server in PolicyLayer and add a rule for slack_find_channel: 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 Work Integrations MCP. Nothing to install.
slack_find_channel 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_find_channel 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_find_channel. 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_find_channel is provided by the Work Integrations MCP server (nazarky/workspace-mcp). 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 →