根据预约人姓名查询预约记录
AI agents call query_reservations_by_name 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 queries and retrieves existing reservation records filtered by name. It performs a read-only operation with no side effects, no data modification, and no resource consumption beyond information disclosure. The severity is low because unauthorized access would expose reservation data, but the tool itself cannot cause irreversible damage or financial harm.
From the tool's definition Tool name 'query_reservations_by_name' and description '根据预约人姓名查询预约记录' (query reservation records by appointee name) indicate a data retrieval operation with no modification or deletion capability.
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_reservations_by_name: 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_by_name 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_by_name 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_by_name. 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_by_name 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 →