files_remote_add · Slack MCP: Risk & Policy

WHAT IT DOES

What files_remote_add does on Slack

AI agents use files_remote_add 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 IT NEEDS A POLICY

Why files_remote_add needs a policy

The 'add' action typically creates or modifies data reversibly. The empty description reduces confidence, but the name strongly implies adding remote file references to Slack—a Write operation. In a Slack context with broad file access, this could modify workspace state and potentially affect collaboration, justifying high severity. Without more detail, confidence is moderate-to-high at 0.72.

From the tool's definition Tool name 'files_remote_add' with 'add' verb indicates creation/modification of remote file references. Description is empty, limiting direct confirmation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

files_remote_add Rate-limited

files_remote_add 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_remote_add": {
      "limits": [
        {
          "counter": "files_remote_add_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Slack, so you can run agents against it safely.

FAQ

Questions about files_remote_add

What does the files_remote_add tool do? +

files_remote_add. 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_remote_add? +

Register the Slack MCP server in PolicyLayer and add a rule for files_remote_add: 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_remote_add? +

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

Can I rate-limit files_remote_add? +

Yes. Add a rate_limit block to the files_remote_add 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_remote_add completely? +

Set action: deny in the PolicyLayer policy for files_remote_add. 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_remote_add? +

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