add_slack_channel_data
AI agents use add_slack_channel_data to create or update resources in Kedro RAG MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kedro RAG MCP environment.
The tool appears to add data to Slack channels, which is a write operation (creates/modifies data reversibly). It's not destructive because additions can theoretically be removed, nor is it financial. However, confidence is moderate because the empty description leaves ambiguity about exact behavior—it could potentially have execute-like qualities if it triggers external operations.
From the tool's definition Tool name 'add_slack_channel_data' indicates it modifies or appends data to a Slack channel dataset. The description is empty, preventing definitive classification, but the verb 'add' combined with 'Slack channel data' suggests a write operation that creates…
Attacks that exploit this kind of access
add_slack_channel_data. It is categorised as a Write tool in the Kedro RAG MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kedro RAG MCP server in PolicyLayer and add a rule for add_slack_channel_data: 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.
add_slack_channel_data is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_slack_channel_data 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 add_slack_channel_data. 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.
add_slack_channel_data 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 →