查询预约窗口
AI agents call query_meet_windows to retrieve information from Reservation System MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves reservation window data without modifying, deleting, or executing code. It is a straightforward query operation that returns information about available appointment windows. The blast radius of misuse is minimal—an agent could only over-query or access window information, with no ability to change records or trigger external effects.
From the tool's definition Tool name 'query_meet_windows' and description '查询预约窗口' (query appointment windows) indicate a retrieval operation. The verb 'query' and '查询' (query/search in Chinese) confirm data retrieval with no modification or deletion.
Attacks that exploit this kind of access
查询预约窗口. It is categorised as a Read tool in the Reservation System MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Reservation System MCP Server MCP server in PolicyLayer and add a rule for query_meet_windows: 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 Reservation System MCP Server. Nothing to install.
query_meet_windows 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 query_meet_windows 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 query_meet_windows. 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.
query_meet_windows is provided by the Reservation System MCP Server MCP server (lingki1/mcp-reservation-server). 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 →