calendar_get_installed_calendars
List the calendar integrations connected to the user (undocumented session endpoint).
This record as markdown: /tools/karbassi-slack-mcp/calendar-get-installed-calendars.md
What calendar_get_installed_calendars does on Slack
AI agents call calendar_get_installed_calendars 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 calendar_get_installed_calendars is rated Low
This tool queries and returns a list of calendar integrations connected to a user. It performs no side effects, does not modify data, does not execute operations, and does not delete or move data. It is a straightforward information retrieval operation.
From the tool's definition Tool name contains 'get' and description states 'List the calendar integrations' — a retrieval operation with no modification or execution. The endpoint is undocumented but the operation itself is read-only.
Attacks that exploit this kind of access
The rule that runs calendar_get_installed_calendars 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_get_installed_calendars, this is the rule to start with:
calendar_get_installed_calendars 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 calendar_get_installed_calendars call is checked against it from then on.
Questions about calendar_get_installed_calendars
List the calendar integrations connected to the user (undocumented session endpoint). 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 calendar_get_installed_calendars: 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.
calendar_get_installed_calendars 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 calendar_get_installed_calendars 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 calendar_get_installed_calendars. 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.
calendar_get_installed_calendars 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