This record as markdown: /tools/deciduus-calendar-mcp/analyze-busyness.md
What analyze_busyness does on Calendar
AI agents call analyze_busyness to retrieve information from Calendar without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why analyze_busyness is rated Low
The tool name and context (calendar analysis, sibling read/query tools) indicate this retrieves and analyzes calendar data without modifying it. No side effects implied. Confidence is moderate due to empty description, but the semantic meaning of 'analyze_busyness' strongly suggests data retrieval rather than modification or execution.
From the tool's definition Tool name 'analyze_busyness' suggests analyzing calendar occupancy/availability patterns. Sibling tools include 'query_free_busy' and calendar query operations, contextualizing this as a read operation. No description provided to confirm exact behavior.
Attacks that exploit this kind of access
The rule that runs analyze_busyness safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Calendar, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For analyze_busyness, this is the rule to start with:
analyze_busyness 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 Calendar, apply this rule, and every analyze_busyness call is checked against it from then on.
Questions about analyze_busyness
analyze_busyness is a read tool on the Calendar MCP server. It is categorised as a Read tool in the Calendar MCP Server, which means it retrieves data without modifying state.
Register the Calendar MCP server in PolicyLayer and add a rule for analyze_busyness: 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 Calendar. Nothing to install.
analyze_busyness 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 analyze_busyness 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 analyze_busyness. 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.
analyze_busyness is provided by the Calendar MCP server (deciduus/calendar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Calendar, and thousands of servers like it.
This server
Across the catalogue