This record as markdown: /tools/karbassi-slack-mcp/team-access-logs.md
What team_access_logs does on Slack
AI agents call team_access_logs to retrieve information from Slack without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why team_access_logs is rated Low
Access logs are typically read-only audit records showing who accessed what and when. The name implies a retrieval/query operation. However, since the description is empty, confidence is reduced. Severity is medium because access logs can contain sensitive authentication and activity data that could be misused if exposed.
From the tool's definition Tool name 'team_access_logs' suggests retrieving access log data; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs team_access_logs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Slack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For team_access_logs, this is the rule to start with:
team_access_logs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Slack, apply this rule, and every team_access_logs call is checked against it from then on.
Questions about team_access_logs
team_access_logs is a read tool on the Slack MCP server. 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 team_access_logs: 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.
team_access_logs 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 team_access_logs 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 team_access_logs. 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.
team_access_logs 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.
More on Slack, and thousands of servers like it.
This server
Across the catalogue