calendar.create

// WHEN AI AGENTS USE THIS TOOL

AI agents use calendar.create to create or modify resources in Hivekey. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON CALENDAR.CREATE

Without a policy, an AI agent could call calendar.create repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Hivekey.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

mailgent-hivekey.yaml

tools:
  calendar.create:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Hivekey policy for all 23 tools.

// DETAILS

Tool Name calendar.create

Category Write

MCP Server Hivekey MCP Server

Risk Level Medium

// MORE HIVEKEY TOOLS

Destructive calendar.delete Destructive mail.delete_message Destructive mail.delete_thread Destructive mail.update_labels Destructive vault.delete Write calendar.update Write mail.send Write vault.store

View all 23 tools →

// WHAT CAN GO WRONG

Agents calling write-class tools like calendar.create have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER WRITE TOOLS ACROSS MCP SERVERS

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

AbraFlexi contact_create AbraFlexi contact_update AbraFlexi evidence_create AbraFlexi evidence_update AbraFlexi invoice_issued_update AbraFlexi invoice_received_create

// RELATED READING

// FAQ

What does the calendar.create tool do? +

Create a new event on this identity's calendar. It is categorised as a Write tool in the Hivekey MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on calendar.create? +

Add a rule in your Intercept YAML policy under the tools section for calendar.create. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Hivekey MCP server.

What risk level is calendar.create? +

calendar.create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit calendar.create? +

Yes. Add a rate_limit block to the calendar.create rule in your Intercept 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.create completely? +

Set action: deny in the Intercept policy for calendar.create. 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.create? +

calendar.create is provided by the Hivekey MCP server (mailgent/hivekey). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Hivekey