workflows_featured_remove
Remove featured workflows from a channel.
This record as markdown: /tools/karbassi-slack-mcp/workflows-featured-remove.md
What workflows_featured_remove does on Slack
AI agents use workflows_featured_remove 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 workflows_featured_remove is rated Medium
Removing featured workflows from a channel modifies the channel's configuration (unfeaturing workflows), but does not permanently delete any data. The workflows still exist and can be re-featured, making this a reversible Write operation rather than Destructive.
From the tool's definition 'Remove featured workflows from a channel' — removes a configuration/association but does not delete the workflow itself; reversible by re-adding.
Attacks that exploit this kind of access
The rule that runs workflows_featured_remove 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 workflows_featured_remove, this is the rule to start with:
workflows_featured_remove 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Slack, apply this rule, and every workflows_featured_remove call is checked against it from then on.
Questions about workflows_featured_remove
Remove featured workflows from a channel. 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.
Register the Slack MCP server in PolicyLayer and add a rule for workflows_featured_remove: 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.
workflows_featured_remove is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the workflows_featured_remove 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 workflows_featured_remove. 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.
workflows_featured_remove 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