Get individual guest reviews for a specific hotel from Google Hotels via SerpAPI. Use this after search_hotels to read actual review text for a hotel. Pass the property_token from a search result. Returns: Individual reviews with full text snippets, ratings, sub-ratings (rooms, service, location)...
AI agents call get_hotel_reviews to retrieve information from Pointsyeah without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward data retrieval tool that searches and fetches hotel review information. It has no side effects, does not modify or delete data, and does not execute arbitrary code or trigger external state changes. The sorting and filtering parameters control how retrieved data is presented, not whether data is modified.
From the tool's definition Tool description explicitly states 'Get individual guest reviews' and 'read actual review text'. Returns reviews with ratings and text snippets.
Attacks that exploit this kind of access
Get individual guest reviews for a specific hotel from Google Hotels via SerpAPI. Use this after search_hotels to read actual review text for a hotel. Pass the property_token from a search result. Returns: Individual reviews with full text snippets, ratings, sub-ratings (rooms, service, location), review dates, reviewer info, hotel highlights, and hotel management responses when available. Sorting: Use sort_by to order reviews: 1 = most helpful (default), 2 = most recent, 3 = highest score, 4 = lowest score. Filtering: Use category_token (from get_hotel_details reviews_breakdown) to filter by category, or source_number to filter by review source. Pagination: The response includes a next_page_token. To get more reviews, call get_hotel_reviews again with the same parameters plus the next_page_token value. It is categorised as a Read tool in the Pointsyeah MCP Server, which means it retrieves data without modifying state.
Register the Pointsyeah MCP server in PolicyLayer and add a rule for get_hotel_reviews: 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 Pointsyeah. Nothing to install.
get_hotel_reviews 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_hotel_reviews 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_hotel_reviews. 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_hotel_reviews is provided by the Pointsyeah MCP server (slack-workspace-mcp-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 →