Use this tool to confirm a meeting. Choose the mode based on how you arrived here:\n
AI agents use createBooking to create or update resources in Mcp Meetsync — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Meetsync environment.
Creating a booking is a Write action—it creates new data (a confirmed meeting) that is persistent and can affect multiple participants' calendars. Severity is high because an AI agent autonomously creating false or unwanted meetings could disrupt schedules, create scheduling conflicts, waste time, and damage relationships.
From the tool's definition Tool name 'createBooking' and description 'Use this tool to confirm a meeting' indicate creation of a new calendar event/booking entry. This is a write operation that modifies calendar data by creating a persistent meeting record.
Attacks that exploit this kind of access
Use this tool to confirm a meeting. Choose the mode based on how you arrived here:\n. It is categorised as a Write tool in the Mcp Meetsync MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Meetsync MCP server in PolicyLayer and add a rule for createBooking: 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 Mcp Meetsync. Nothing to install.
createBooking 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 createBooking 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 createBooking. 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.
createBooking is provided by the Mcp Meetsync MCP server (nicholasemccormick/mcp-meetsync). 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 →