Searches for attractions and points of interest in a specified location
AI agents call search_attractions to retrieve information from Server Travelplanner without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
radius | number | — | Search radius in meters |
location | string | Yes | Location to search attractions |
categories | array | — | Categories of attractions |
Parameters from the server's own tool schema.
This tool retrieves information about attractions without modifying, executing external operations, or deleting data. It is a straightforward read operation that returns query results. The blast radius of misuse is minimal — an agent could only be given irrelevant attraction suggestions, causing inconvenience rather than harm.
From the tool's definition Tool name 'search_attractions' and description states it 'Searches for attractions and points of interest in a specified location' — a query operation with no side effects.
Attacks that exploit this kind of access
Searches for attractions and points of interest in a specified location. It is categorised as a Read tool in the Server Travelplanner MCP Server, which means it retrieves data without modifying state.
search_attractions accepts 3 parameters: radius, location, categories. Required: location. The full parameter table on this page comes from the server's own tool schema.
Register the Server Travelplanner MCP server in PolicyLayer and add a rule for search_attractions: 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 Server Travelplanner. Nothing to install.
search_attractions 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 search_attractions 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 search_attractions. 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.
search_attractions is provided by the Server Travelplanner MCP server (@gongrzhe/server-travelplanner-mcp). 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 →