This record as markdown: /tools/karbassi-slack-mcp/activity-feed.md
What activity_feed does on Slack
AI agents call activity_feed 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.
Why activity_feed is rated Low
The tool name 'activity_feed' suggests a read operation that fetches or lists activity events from Slack. However, the description is empty, which significantly lowers confidence. On a Slack MCP server with 220 tools, this most likely retrieves activity data (notifications, events, actions) without side effects.
From the tool's definition Tool name 'activity_feed' and empty description. Based on the name alone, this likely retrieves/queries an activity feed.
Attacks that exploit this kind of access
The rule that runs activity_feed 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 activity_feed, this is the rule to start with:
activity_feed is read-only, so it stays allowed. 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 activity_feed call is checked against it from then on.
Questions about activity_feed
activity_feed is a read tool on the Slack MCP server. It is categorised as a Read tool in the Slack MCP Server, which means it retrieves data without modifying state.
Register the Slack MCP server in PolicyLayer and add a rule for activity_feed: 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.
activity_feed 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 activity_feed 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 activity_feed. 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.
activity_feed 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