files_share_legacy

Share a file to a channel (legacy undocumented).

SERVERSlack SOURCEkarbassi/slack-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/karbassi-slack-mcp/files-share-legacy.md

WHAT IT DOES

What files_share_legacy does on Slack

AI agents use files_share_legacy 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.

RISK

Why files_share_legacy is rated Medium

This tool creates a new sharing relationship between a file and a channel, which is a reversible modification of data/permissions. It does not delete data (ruling out Destructive), does not execute arbitrary code (ruling out Execute), and does not involve financial transactions (ruling out Financial).

From the tool's definition Tool name contains 'share' and description states 'Share a file to a channel', indicating it modifies access permissions and channel state by distributing a file resource.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs files_share_legacy 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_share_legacy, this is the rule to start with:

files_share_legacy Rate-limited

files_share_legacy 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "files_share_legacy": {
      "limits": [
        {
          "counter": "files_share_legacy_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Slack, apply this rule, and every files_share_legacy call is checked against it from then on.

FAQ

Questions about files_share_legacy

What does the files_share_legacy tool do? +

Share a file to a channel (legacy undocumented). 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.

How do I enforce a policy on files_share_legacy? +

Register the Slack MCP server in PolicyLayer and add a rule for files_share_legacy: 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.

What risk level is files_share_legacy? +

files_share_legacy is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit files_share_legacy? +

Yes. Add a rate_limit block to the files_share_legacy 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.

How do I block files_share_legacy completely? +

Set action: deny in the PolicyLayer policy for files_share_legacy. 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.

What MCP server provides files_share_legacy? +

files_share_legacy 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.

KEEP EXPLORING

More on Slack, and thousands of servers like it.

This server

All 233 Slack tools →

Across the catalogue

scaffold_project_files on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →