slack_delete_message
AI agents call slack_delete_message to permanently remove resources in Mcp Gmail — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Message deletion is irreversible and removes data permanently. Although the tool is named 'slack_delete_message' and appears to be from a Slack integration (not Gmail directly), the sibling tools listed are GitHub-related (issues, projects, PRs), suggesting this may be a multi-service MCP server. Regardless, deletion operations fall into the Destructive category due to their irreversible nature.
From the tool's definition Tool name 'slack_delete_message' indicates permanent deletion of message data. The description is empty, but the naming convention is unambiguous.
Attacks that exploit this kind of access
slack_delete_message. It is categorised as a Destructive tool in the Mcp Gmail MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Gmail MCP server in PolicyLayer and add a rule for slack_delete_message: 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 Gmail. Nothing to install.
slack_delete_message 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 slack_delete_message 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_delete_message. 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_delete_message is provided by the Mcp Gmail MCP server (@monsoft/mcp-gmail). 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 →