Manage calendar events. Actions: list, get, create, update, delete. All times are stored in UTC — when querying for a local date range, offset filterDateFrom/filterDateTo to account for the company timezone (e.g. for NZDT/UTC+13, subtract 13 hours from the local start/end). For list: send filterD...
AI agents use manage-calendar-events to create or update resources in Fergus MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fergus MCP Server environment.
The tool spans multiple categories: Read (list, get), Write (create, update), and Destructive (delete). Following the severity hierarchy, Destructive is most severe. However, the primary operations appear to be event management (create/update), and while delete is mentioned, calendar event deletion is typically reversible in most systems (soft deletes or recovery possible).
From the tool's definition Tool supports create, update, and delete actions on calendar events. The description explicitly lists 'Actions: list, get, create, update, delete' which includes reversible write and destructive operations.
Attacks that exploit this kind of access
Manage calendar events. Actions: list, get, create, update, delete. All times are stored in UTC — when querying for a local date range, offset filterDateFrom/filterDateTo to account for the company timezone (e.g. for NZDT/UTC+13, subtract 13 hours from the local start/end). For list: send filterDateFrom with a timezone offset (e.g. 2026-03-27T00:00:00+13:00) so the partner API computes correct day boundaries. Use filterCalendarRange to control the date window (DAY, WEEK, etc.). Note: filterDateTo is not supported by the partner API and will be ignored. It is categorised as a Write tool in the Fergus MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fergus MCP Server MCP server in PolicyLayer and add a rule for manage-calendar-events: 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 Fergus MCP Server. Nothing to install.
manage-calendar-events 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 manage-calendar-events 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 manage-calendar-events. 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.
manage-calendar-events is provided by the Fergus MCP Server MCP server (jayco-design/fergus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →