files_get_shares

Get where a file has been shared (undocumented).

SERVERSlack SOURCEkarbassi/slack-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/karbassi-slack-mcp/files-get-shares.md

WHAT IT DOES

What files_get_shares does on Slack

AI agents call files_get_shares to retrieve information from Slack without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why files_get_shares is rated Low

This tool queries metadata about file sharing distribution without modifying, executing operations, or deleting data. While the read access is over potentially sensitive sharing information (which could expose organizational structure or collaboration patterns), the lack of side effects and irreversibility places it in Read category.

From the tool's definition Tool name is 'files_get_shares' with description 'Get where a file has been shared'. The verb 'Get' and action 'retrieves' information about file sharing locations indicate a read-only query operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

files_get_shares Allowed

files_get_shares is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "files_get_shares": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about files_get_shares

What does the files_get_shares tool do? +

Get where a file has been shared (undocumented). It is categorised as a Read tool in the Slack MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on files_get_shares? +

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

files_get_shares is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit files_get_shares? +

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

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

files_get_shares 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →