team_access_logs

team_access_logs

Server Slack karbassi/slack-mcp
Category Read
Risk class Low
Parameters 00 required

What team_access_logs does on Slack

AI agents call team_access_logs 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.

Why team_access_logs needs a policy

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.

Questions about team_access_logs

What does the team_access_logs tool do? +

team_access_logs. It is categorised as a Read tool in the Slack MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on team_access_logs? +

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.

What risk level is team_access_logs? +

team_access_logs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit team_access_logs? +

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.

How do I block team_access_logs completely? +

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.

What MCP server provides team_access_logs? +

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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.