search_places
Place/address geocoding (OpenStreetMap) — full address, category, lat/lng for any landmark/location. For maps, logistics Cost: $0.005–$0.05 USDC on Base per call.
This record as markdown: /tools/com-gocreativeai-omnicall-agent-tools/search-places.md
What search_places does on Omnicall — Agent Tools Gateway
AI agents call search_places to retrieve information from Omnicall — Agent Tools Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
arg | string | Yes |
Parameters from the server's own tool schema.
Why search_places is rated Low
This tool performs geographic lookups and coordinate retrieval, which are fundamentally read operations. There is no creation, modification, deletion, code execution, or financial impact beyond the stated pay-per-call cost model. The use case ('For maps, logistics') confirms informational use. The cost is a standard API fee, not a financial transaction initiated by the tool itself.
From the tool's definition Tool description explicitly states 'Place/address geocoding (OpenStreetMap)' and lists outputs as 'full address, category, lat/lng for any landmark/location'. These are read-only queries that retrieve location data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs search_places safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Omnicall — Agent Tools Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_places, this is the rule to start with:
search_places is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Omnicall — Agent Tools Gateway, apply this rule, and every search_places call is checked against it from then on.
Questions about search_places
Place/address geocoding (OpenStreetMap) — full address, category, lat/lng for any landmark/location. For maps, logistics Cost: $0.005–$0.05 USDC on Base per call. It is categorised as a Read tool in the Omnicall — Agent Tools Gateway MCP Server, which means it retrieves data without modifying state.
search_places accepts 1 parameter: arg. Required: arg. The full parameter table on this page comes from the server's own tool schema.
Register the Omnicall — Agent Tools Gateway MCP server in PolicyLayer and add a rule for search_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 Omnicall — Agent Tools Gateway. Nothing to install.
search_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 search_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 search_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.
search_places is provided by the Omnicall — Agent Tools Gateway MCP server (https://omnicall.gocreativeai.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Omnicall — Agent Tools Gateway, and thousands of servers like it.
This server
Across the catalogue