Critical Risk →

SLACK_REMOVE_A_STAR_FROM_AN_ITEM

Removes a star from a previously starred Slack item (message, file, file comment, channel, group, or DM), requiring identification via `file`, `file_comment`, `channel` (for channel/group/DM), or both `channel` and `timestamp` (for a message).

Accepts file system path (file)

Part of the Slack MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@modelcontextprotocol/server-slack Destructive Risk 5/5

AI agents may call SLACK_REMOVE_A_STAR_FROM_AN_ITEM to permanently remove or destroy resources in Slack. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call SLACK_REMOVE_A_STAR_FROM_AN_ITEM in a loop, permanently destroying resources in Slack. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

slack.yaml
tools:
  SLACK_REMOVE_A_STAR_FROM_AN_ITEM:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Slack policy for all 143 tools.

Tool Name SLACK_REMOVE_A_STAR_FROM_AN_ITEM
Category Destructive
MCP Server Slack MCP Server
Risk Level Critical

View all 143 tools →

Agents calling destructive-class tools like SLACK_REMOVE_A_STAR_FROM_AN_ITEM have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

SLACK_REMOVE_A_STAR_FROM_AN_ITEM is one of the critical-risk operations in Slack. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the SLACK_REMOVE_A_STAR_FROM_AN_ITEM tool do? +

Removes a star from a previously starred Slack item (message, file, file comment, channel, group, or DM), requiring identification via `file`, `file_comment`, `channel` (for channel/group/DM), or both `channel` and `timestamp` (for a message).. 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.

How do I enforce a policy on SLACK_REMOVE_A_STAR_FROM_AN_ITEM? +

Add a rule in your Intercept YAML policy under the tools section for SLACK_REMOVE_A_STAR_FROM_AN_ITEM. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Slack MCP server.

What risk level is SLACK_REMOVE_A_STAR_FROM_AN_ITEM? +

SLACK_REMOVE_A_STAR_FROM_AN_ITEM is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit SLACK_REMOVE_A_STAR_FROM_AN_ITEM? +

Yes. Add a rate_limit block to the SLACK_REMOVE_A_STAR_FROM_AN_ITEM rule in your Intercept 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 SLACK_REMOVE_A_STAR_FROM_AN_ITEM completely? +

Set action: deny in the Intercept policy for SLACK_REMOVE_A_STAR_FROM_AN_ITEM. 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 SLACK_REMOVE_A_STAR_FROM_AN_ITEM? +

SLACK_REMOVE_A_STAR_FROM_AN_ITEM is provided by the Slack MCP server (@modelcontextprotocol/server-slack). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Slack

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.