This record as markdown: /tools/deciduus-calendar-mcp/schedule-mutual.md
What schedule_mutual does on Calendar
AI agents use schedule_mutual to create or update resources in Calendar, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Calendar environment.
Why schedule_mutual is rated Medium
Given the calendar context and sibling tools, 'schedule_mutual' likely finds a mutually available time slot and schedules/creates an event for multiple attendees, which is a Write operation. Confidence is low due to empty description — it could also be a Read (just finding availability) or Execute (triggering invites). Write is the most reasonable guess given the 'schedule' prefix implies creation.
From the tool's definition Tool name 'schedule_mutual' on a calendar server alongside siblings like 'create_event', 'add_attendee', 'find_events'. Description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs schedule_mutual 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 schedule_mutual, this is the rule to start with:
schedule_mutual stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 schedule_mutual call is checked against it from then on.
Questions about schedule_mutual
schedule_mutual is a write tool on the Calendar MCP server. It is categorised as a Write tool in the Calendar MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Calendar MCP server in PolicyLayer and add a rule for schedule_mutual: 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.
schedule_mutual is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the schedule_mutual 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 schedule_mutual. 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.
schedule_mutual 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