Use this tool when you need to retrieve confirmed, cancelled, or rescheduled meetings.
AI agents call listBookings to retrieve information from Mcp Meetsync without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
listBookings retrieves calendar booking data without modifying, creating, or destroying any records. The verb 'retrieve' and the read-only nature of listing existing bookings clearly indicate this is a Read operation. Severity is low because the tool only accesses calendar metadata without affecting calendar state or triggering external actions.
From the tool's definition Tool description states 'retrieve confirmed, cancelled, or rescheduled meetings' — a query operation with no modification, deletion, or side effects.
Attacks that exploit this kind of access
Use this tool when you need to retrieve confirmed, cancelled, or rescheduled meetings. It is categorised as a Read tool in the Mcp Meetsync MCP Server, which means it retrieves data without modifying state.
Register the Mcp Meetsync MCP server in PolicyLayer and add a rule for listBookings: 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.
listBookings is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the listBookings 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 listBookings. 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.
listBookings 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 →