Check the status of a reservation request by session ID. Requires the access_token that was returned in the create_reservation_request response. You MUST have stored the access_token from the create response to use this tool. Without a valid access_token, the API will return 403 Forbidden. IMPORT...
Risk signalsHandles credentials or secrets (access_token)
Part of the Mcp server.
Free to start. No card required.
AI agents call get_reservation_request_status to retrieve information from Mcp without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_reservation_request_status only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_reservation_request_status": {}
}
}See the full Mcp policy for all 11 tools.
These attack patterns abuse exactly the kind of access get_reservation_request_status gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Check the status of a reservation request by session ID. Requires the access_token that was returned in the create_reservation_request response. You MUST have stored the access_token from the create response to use this tool. Without a valid access_token, the API will return 403 Forbidden. IMPORTANT - PRICE DISPLAY: The "price" field already INCLUDES the "booking_fee". Do NOT add them together. When displaying to the user, show: price (total) and booking_fee (included in price, non-refundable). Example: "Total: ¥30,000 (includes ¥1,000 non-refundable booking fee)". It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for get_reservation_request_status: 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. Nothing to install.
get_reservation_request_status 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 get_reservation_request_status 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 get_reservation_request_status. 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.
get_reservation_request_status is provided by the MCP server (https://mcp.tableall.com/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 Mcp tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.