查询预约记录，支持按用户ID、状态、预约项目ID等条件筛选
AI agents call query_reservations 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 is a query/search operation that retrieves and filters existing reservation data without modifying, deleting, or executing external operations. It has no side effects beyond data retrieval. While the server contains destructive tools (delete_*), this specific tool is purely informational.
From the tool's definition Tool name 'query_reservations' and description '查询预约记录，支持按用户ID、状态、预约项目ID等条件筛选' (Query reservation records, supports filtering by user ID, status, reservation item ID, etc.) indicate data retrieval with filtering capabilities only.
Attacks that exploit this kind of access
查询预约记录，支持按用户ID、状态、预约项目ID等条件筛选. 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_reservations: 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_reservations 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_reservations 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_reservations. 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_reservations 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 →