AI agents call slack_get_channel_history to retrieve information from Mcp Gmail without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name strongly suggests a read operation that queries and retrieves historical data from a Slack channel with no side effects. However, confidence is reduced to 0.6 because the description is empty and cannot corroborate the function, and there is a contextual mismatch (the server is advertised as 'Mcp Gmail' yet this tool references Slack).
From the tool's definition Tool name 'slack_get_channel_history' indicates retrieval of message history from a Slack channel. The description is empty, limiting certainty.
Attacks that exploit this kind of access
slack_get_channel_history. It is categorised as a Read tool in the Mcp Gmail MCP Server, which means it retrieves data without modifying state.
Register the Mcp Gmail MCP server in PolicyLayer and add a rule for slack_get_channel_history: 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_get_channel_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the slack_get_channel_history 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_get_channel_history. 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_get_channel_history 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 →