AI agents use slack_share_file to create or update resources in Mcp Gmail — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Gmail environment.
File sharing typically creates records or modifies access permissions in the destination system (Slack), making it a Write operation. However, the empty description and the tool's presence on a Gmail/GitHub MCP server (rather than a Slack-native server) creates some uncertainty. The confidence is moderate due to missing documentation.
From the tool's definition Tool name 'slack_share_file' indicates file sharing capability, which creates or modifies shared state. Description is empty, preventing full assessment.
Attacks that exploit this kind of access
slack_share_file. It is categorised as a Write tool in the Mcp Gmail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Gmail MCP server in PolicyLayer and add a rule for slack_share_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_share_file 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 slack_share_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_share_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_share_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 →