This record as markdown: /tools/karbassi-slack-mcp/pins-remove.md
What pins_remove does on Slack
AI agents call pins_remove to permanently remove resources in Slack, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why pins_remove is rated Critical
Unpinning an item removes its pinned status from a channel. While the underlying message or file is not deleted, the pin itself is irreversibly removed (there is no 'restore pin' operation), making this a destructive action. Misuse by an AI agent could silently remove important pinned references from channels, with medium blast radius since it affects organizational context but not the underlying content.
From the tool's definition "Unpin an item from a channel" — removing a pin is an action that cannot be trivially undone through the same tool; the pin state is permanently removed.
Attacks that exploit this kind of access
The rule that runs pins_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 pins_remove, this is the rule to start with:
pins_remove is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Slack, apply this rule, and every pins_remove call is checked against it from then on.
Questions about pins_remove
Unpin an item from a channel. It is categorised as a Destructive tool in the Slack MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Slack MCP server in PolicyLayer and add a rule for pins_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.
pins_remove is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the pins_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 pins_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.
pins_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.
Across the catalogue