inaturalist.places.search
Look up an iNaturalist place_id by name, e.g. "Berlin" or "Yellowstone National Park", for use with inaturalist.observations_search and inaturalist.species_counts. Returns matching places with their place_id, display name, and place type (e.g. town, county, park). Data: iNaturalist.org global cit...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/inaturalist.places.search.md
What inaturalist.places.search does on Apibase
AI agents call inaturalist.places.search to retrieve information from Apibase 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 |
|---|---|---|---|
query | string | Yes | Place name to search for, e.g. "Berlin" or "Yellowstone National Park". |
per_page | integer | — | Number of results to return, 1-20 (default 10). |
Parameters from the server's own tool schema.
Why inaturalist.places.search is rated Low
Tool queries public iNaturalist data and returns location identifiers with no side effects.
From the tool's definition Look up iNaturalist place_id by name, returns matching places with place_id and display name
Attacks that exploit this kind of access
The rule that runs inaturalist.places.search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For inaturalist.places.search, this is the rule to start with:
inaturalist.places.search 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 Apibase, apply this rule, and every inaturalist.places.search call is checked against it from then on.
Questions about inaturalist.places.search
Look up an iNaturalist place_id by name, e.g. "Berlin" or "Yellowstone National Park", for use with inaturalist.observations_search and inaturalist.species_counts. Returns matching places with their place_id, display name, and place type (e.g. town, county, park). Data: iNaturalist.org global citizen-science community, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
inaturalist.places.search accepts 2 parameters: query, per_page. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for inaturalist.places.search: 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 Apibase. Nothing to install.
inaturalist.places.search 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 inaturalist.places.search 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 inaturalist.places.search. 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.
inaturalist.places.search is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue