schedule_meeting

SERVERStarfield SOURCE@adrata/starfield-mcp

Medium RISK CLASS

Category Write

Parameters 113 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-starfield-mcp/schedule-meeting.md

WHAT IT DOES

What schedule_meeting does on Starfield

AI agents use schedule_meeting 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.

Parameter	Type	Required	Description
`date`	string	Yes	Date in YYYY-MM-DD format
`time`	string	Yes	Time in HH:MM 24h format
`title`	string	Yes	Meeting title
`dryRun`	boolean	—	Defaults to true. Set false after explicit approval to request a confirmation token.
`reason`	string	—	Required audit reason when requesting a live-write confirmation token.
`eventId`	string	—	Existing Adrata event ID to update instead of creating a duplicate
`duration`	number	—	Duration in minutes (default 30)
`timezone`	string	—	IANA timezone. Auto-detected if omitted.
`attendees`	array	—	List of attendee email addresses
`description`	string	—	Meeting description or agenda
`confirmationToken`	string	—	Single-use server token from the approved first request.

Parameters from the server's own tool schema.

RISK

Why schedule_meeting is rated Medium

An AI agent can call schedule_meeting 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.

Risk signalsHigh parameter count (11 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs schedule_meeting safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Starfield, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For schedule_meeting, this is the rule to start with:

schedule_meeting Rate-limited

schedule_meeting 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "schedule_meeting": {
      "limits": [
        {
          "counter": "schedule_meeting_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Starfield, apply this rule, and every schedule_meeting call is checked against it from then on.

FAQ

Questions about schedule_meeting

What does the schedule_meeting tool do? +

Preview or create a meeting through Adrata chat’s governed calendar path. Live creation requires an audit reason and the server-issued confirmation token returned by the first approved request. Provider delivery remains pending until sync confirms it. 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 schedule_meeting accept? +

schedule_meeting accepts 11 parameters: date, time, title, dryRun, reason, eventId, duration, timezone, attendees, description, confirmationToken. Required: date, time, title. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on schedule_meeting? +

Register the Starfield MCP server in PolicyLayer and add a rule for schedule_meeting: 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 schedule_meeting? +

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

Can I rate-limit schedule_meeting? +

Yes. Add a rate_limit block to the schedule_meeting 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 schedule_meeting completely? +

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

schedule_meeting 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.

KEEP EXPLORING

More on Starfield, and thousands of servers like it.

This server

All 233 Starfield tools →

Across the catalogue

sms_schedule on Twilio SMS MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →