AI agents call apps_event_authorizations_list to retrieve information from Slack without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve or enumerate event authorizations for apps, which is a read operation with no side effects. Severity is medium rather than low because authorization data is sensitive and could reveal security posture or app permissions if exfiltrated by a compromised agent.
From the tool's definition Tool name 'apps_event_authorizations_list' indicates a listing/retrieval operation on authorization data. The 'list' suffix and context within Slack's API families suggest querying existing authorizations rather than modifying them.
Attacks that exploit this kind of access
apps_event_authorizations_list. It is categorised as a Read tool in the Slack MCP Server, which means it retrieves data without modifying state.
Register the Slack MCP server in PolicyLayer and add a rule for apps_event_authorizations_list: 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. Nothing to install.
apps_event_authorizations_list 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 apps_event_authorizations_list 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 apps_event_authorizations_list. 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.
apps_event_authorizations_list is provided by the Slack MCP server (karbassi/slack-mcp). 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 →