Use this tool when you need to retrieve full details about a specific booking —
AI agents call getBooking 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.
The tool performs a read-only query to fetch booking information. There are no side effects, no data modification, and no execution of external operations. It falls squarely within the Read category. The severity is low because retrieving booking details poses minimal risk—an agent misusing this tool would only gain access to information that already exists, with no ability to modify, delete, or trigger actions.
From the tool's definition Tool name is 'getBooking' and description states it retrieves 'full details about a specific booking' with no mention of modification, deletion, or execution. This is a pure retrieval operation.
Attacks that exploit this kind of access
Use this tool when you need to retrieve full details about a specific booking —. 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 getBooking: 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.
getBooking 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 getBooking 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 getBooking. 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.
getBooking 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 →