calendar_user_status

A read tool on the Slack MCP server.

SERVERSlack SOURCEkarbassi/slack-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/karbassi-slack-mcp/calendar-user-status.md

WHAT IT DOES

What calendar_user_status does on Slack

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

RISK

Why calendar_user_status is rated Low

Based on the tool name alone, this appears to query or retrieve user calendar and status data from Slack without modifying it. With an empty description, confidence is moderate. The naming convention (read-like verbs in similar Slack tools) and the informational nature of 'status' suggests this is a Read operation.

From the tool's definition Tool name 'calendar_user_status' indicates retrieval of calendar and user status information. Description is empty, limiting evidence strength.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs calendar_user_status 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 calendar_user_status, this is the rule to start with:

calendar_user_status Allowed

calendar_user_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "calendar_user_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Slack, apply this rule, and every calendar_user_status call is checked against it from then on.

FAQ

Questions about calendar_user_status

What does the calendar_user_status tool do? +

calendar_user_status 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.

How do I enforce a policy on calendar_user_status? +

Register the Slack MCP server in PolicyLayer and add a rule for calendar_user_status: 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 calendar_user_status? +

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

Can I rate-limit calendar_user_status? +

Yes. Add a rate_limit block to the calendar_user_status 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 calendar_user_status completely? +

Set action: deny in the PolicyLayer policy for calendar_user_status. 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 calendar_user_status? +

calendar_user_status 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.

KEEP EXPLORING

More on Slack, and thousands of servers like it.

This server

All 233 Slack tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →