This record as markdown: /tools/karbassi-slack-mcp/files-upload.md
What files_upload does on Slack
AI agents use files_upload to create or update resources in Slack, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Slack environment.
Why files_upload is rated Medium
File uploads create new data or modify existing file storage in Slack. This is reversible (files can be deleted), so it is Write rather than Destructive. Severity is high because an AI agent could upload malicious files, credentials, or sensitive content to shared workspaces without authorization, with broad organizational impact.
From the tool's definition Tool name 'files_upload' combined with server description stating 'Provides LLMs full access to Slack: messages, channels, files, canvases, lists' indicates file creation/modification capability.
Attacks that exploit this kind of access
The rule that runs files_upload 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 files_upload, this is the rule to start with:
files_upload stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 files_upload call is checked against it from then on.
Questions about files_upload
files_upload is a write tool on the Slack MCP server. It is categorised as a Write tool in the Slack MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Slack MCP server in PolicyLayer and add a rule for files_upload: 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.
files_upload 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 files_upload 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 files_upload. 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.
files_upload 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