Find where a specific bird species has been seen recently near a location, sorted by most recent observation.
AI agents call species_finder to retrieve information from Birding Planner without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries historical birding observation data (from eBird/iNaturalist integration) to return location and timing information about bird sightings. It has no side effects, cannot modify data, execute code, delete records, or affect financial systems. It is a straightforward read operation suitable for trip planning research.
From the tool's definition Tool description states it 'find[s] where a specific bird species has been seen recently' and is 'sorted by most recent observation' — purely a data retrieval operation with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Find where a specific bird species has been seen recently near a location, sorted by most recent observation. It is categorised as a Read tool in the Birding Planner MCP Server, which means it retrieves data without modifying state.
Register the Birding Planner MCP server in PolicyLayer and add a rule for species_finder: 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 Birding Planner. Nothing to install.
species_finder 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 species_finder 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 species_finder. 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.
species_finder is provided by the Birding Planner MCP server (minikdj/ebird-birding-planner). 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 →