New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

paper_create_calendar_event

Create a Paper calendar event. Live writes require dryRun:false, approved:true, reason, and idempotencyKey.

SERVERStarfield SOURCE@adrata/starfield-mcp
Medium RISK CLASS
Category Write
Parameters 93 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-starfield-mcp/paper-create-calendar-event.md

What paper_create_calendar_event does on Starfield

AI agents use paper_create_calendar_event to create or update resources in Starfield, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Starfield environment.

ParameterTypeRequiredDescription
title string Yes
dryRun boolean Defaults to true. Set false only after explicit user approval.
reason string Audit reason for live writes.
endTime string Yes
approved boolean Must be true for live writes.
location string
attendees array
startTime string Yes
idempotencyKey string Required for live writes.

Parameters from the server's own tool schema.

Why paper_create_calendar_event is rated Medium

An AI agent can call paper_create_calendar_event faster than any human can review: one bad instruction and it creates or modifies resources in Starfield by the hundred, each call as confident as the last.

Questions about paper_create_calendar_event

What does the paper_create_calendar_event tool do? +

Create a Paper calendar event. Live writes require dryRun:false, approved:true, reason, and idempotencyKey. It is categorised as a Write tool in the Starfield MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does paper_create_calendar_event accept? +

paper_create_calendar_event accepts 9 parameters: title, dryRun, reason, endTime, approved, location, attendees, startTime, idempotencyKey. Required: title, endTime, startTime. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on paper_create_calendar_event? +

Register the Starfield MCP server in PolicyLayer and add a rule for paper_create_calendar_event: 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 Starfield. Nothing to install.

What risk level is paper_create_calendar_event? +

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

Can I rate-limit paper_create_calendar_event? +

Yes. Add a rate_limit block to the paper_create_calendar_event 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.

How do I block paper_create_calendar_event completely? +

Set action: deny in the PolicyLayer policy for paper_create_calendar_event. 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 paper_create_calendar_event? +

paper_create_calendar_event is provided by the Starfield MCP server (@adrata/starfield-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Starfield, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Starfield's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.