find_nearby_places
AI agents call find_nearby_places to retrieve information from openwebui-tools MCP server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name indicates a search or lookup function for geographic data (Read category). Without a description, we cannot confirm destructive, financial, or execute capabilities. The sibling tools on this server (fetch_page, get_company_data, query_wolfram_alpha, search_web, send_email) are primarily Read-oriented (except send_email, which is Write), suggesting this tool follows a similar pattern.
From the tool's definition Tool name 'find_nearby_places' suggests a location-based query operation with no apparent side effects. However, the description is empty, making definitive classification difficult.
Attacks that exploit this kind of access
find_nearby_places. It is categorised as a Read tool in the openwebui-tools MCP server MCP Server, which means it retrieves data without modifying state.
Register the openwebui-tools MCP server MCP server in PolicyLayer and add a rule for find_nearby_places: 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 openwebui-tools MCP server. Nothing to install.
find_nearby_places 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 find_nearby_places 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 find_nearby_places. 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.
find_nearby_places is provided by the openwebui-tools MCP server MCP server (madelponte/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 →