Get all species ever recorded in a region — returns species codes
AI agents call get_species_list to retrieve information from Birding Buddy MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the eBird API to retrieve historical species occurrence data for a geographic region. It has no side effects, does not create, modify, or delete data, and poses no risk of misuse beyond potentially returning large datasets. It is a straightforward read operation consistent with birding research and life list planning.
From the tool's definition Tool description explicitly states it 'returns species codes' from a region without modifying data. The verb 'Get' and sibling tools (check_life_list, get_hotspot_observations, get_historic_observations) confirm this is a retrieval operation.
Attacks that exploit this kind of access
Get all species ever recorded in a region — returns species codes. It is categorised as a Read tool in the Birding Buddy MCP MCP Server, which means it retrieves data without modifying state.
Register the Birding Buddy MCP server in PolicyLayer and add a rule for get_species_list: 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 Buddy MCP. Nothing to install.
get_species_list 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 get_species_list 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 get_species_list. 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.
get_species_list is provided by the Birding Buddy MCP server (woodcreeper/birding-buddy-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 →