list_slack_channels
AI agents call list_slack_channels to retrieve information from Kedro RAG MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or enumerates Slack channels—a read-only operation with no side effects. Even if it returns sensitive channel metadata, the action itself does not modify, delete, or execute operations. Confidence is moderate (0.7) because the description is empty, requiring inference from the name and sibling tools.
From the tool's definition Tool name 'list_slack_channels' indicates retrieval of channel information. The description is empty, but the name and context (sibling tool 'add_slack_channel_data' suggests Slack integration) indicate a listing/query operation.
Attacks that exploit this kind of access
list_slack_channels. It is categorised as a Read tool in the Kedro RAG MCP MCP Server, which means it retrieves data without modifying state.
Register the Kedro RAG MCP server in PolicyLayer and add a rule for list_slack_channels: 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 Kedro RAG MCP. Nothing to install.
list_slack_channels 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 list_slack_channels 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 list_slack_channels. 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.
list_slack_channels is provided by the Kedro RAG MCP server (sajidalamqb/kedro-mcp-rag). 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 →