View the full species list for a specific eBird checklist. The subId can come from get_recent_checklists or directly from observation results which already include subId in their payload — in that case call this directly with no extra queries needed. WARNING: Never call this in a loop or batch ac...
AI agents call view_checklist 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 retrieves and displays data from eBird checklists without side effects. The explicit instruction to avoid batching suggests rate-limiting concerns rather than safety risks from the operation itself. No data is created, modified, deleted, or financial operations are involved. This is a straightforward read/query operation.
From the tool's definition Tool name 'view_checklist' and description states it 'View[s] the full species list' — a retrieval operation. The warning against looping indicates it queries an API but does not modify, delete, or execute arbitrary operations.
Attacks that exploit this kind of access
View the full species list for a specific eBird checklist. The subId can come from get_recent_checklists or directly from observation results which already include subId in their payload — in that case call this directly with no extra queries needed. WARNING: Never call this in a loop or batch across multiple subIds. One call per explicit user request only. 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 view_checklist: 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.
view_checklist 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 view_checklist 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 view_checklist. 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.
view_checklist 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 →