AI agents call slack_list_files to retrieve information from MCP Slack without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name and naming pattern ('list_files') clearly indicate data retrieval without modification. The server is explicitly described as 'read-only', and all sibling tools are retrieval operations (list, get). No side effects, mutation, or destruction are possible.
From the tool's definition Tool name 'slack_list_files' indicates a list/query operation. Empty description, but consistent with sibling tools like 'slack_list_channels' and 'slack_get_file_info' on a 'Secure read-only MCP server for Slack workspaces' that all perform retrieval…
Attacks that exploit this kind of access
slack_list_files. It is categorised as a Read tool in the MCP Slack MCP Server, which means it retrieves data without modifying state.
Register the MCP Slack MCP server in PolicyLayer and add a rule for slack_list_files: 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 MCP Slack. Nothing to install.
slack_list_files is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the slack_list_files 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 slack_list_files. 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.
slack_list_files is provided by the MCP Slack MCP server (pypi:mcp-slack-crunchtools). 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 →