slack_delete_file
AI agents call slack_delete_file 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.
Deletion of files cannot be undone and represents permanent data loss. This is a Destructive action with high severity due to potential data loss impact. The empty description lowers confidence from critical to high. Note: This tool appears misattributed to a Gmail MCP server but is actually a Slack operation, which is unusual for the server context.
From the tool's definition Tool name 'slack_delete_file' indicates irreversible deletion of files. Description is empty, reducing confidence slightly, but the name and destructive semantics are clear.
Attacks that exploit this kind of access
slack_delete_file. 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_file: 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_file 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_file 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_file. 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_file 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 →