Obter analytics de um canal (atividade, engajamento)
AI agents call get_channel_analytics to retrieve information from Slack MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries analytics data about channel activity and engagement metrics. It has no side effects—it does not create, modify, delete, or execute operations. It is a straightforward Read operation analogous to 'get' or 'fetch' operations.
From the tool's definition Tool name 'get_channel_analytics' and description 'Obter analytics de um canal (atividade, engajamento)' [Get analytics from a channel (activity, engagement)] indicates data retrieval only. No modification, deletion, or external execution occurs.
Attacks that exploit this kind of access
Obter analytics de um canal (atividade, engajamento). It is categorised as a Read tool in the Slack MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Slack MCP Server MCP server in PolicyLayer and add a rule for get_channel_analytics: 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 Slack MCP Server. Nothing to install.
get_channel_analytics 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 get_channel_analytics 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 get_channel_analytics. 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.
get_channel_analytics is provided by the Slack MCP Server MCP server (will2023a/mcp-slack). 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 →