get_recent_checklists

Get recent checklists submitted at a hotspot or in a region. Returns subId for each checklist so a specific one can be viewed with view_checklist. Use resolve_hotspot first if you only have a hotspot name.

Server Birding Buddy MCP woodcreeper/birding-buddy-mcp
Category Read
Risk class Low
Parameters 00 required

What get_recent_checklists does on Birding Buddy MCP

AI agents call get_recent_checklists 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.

Why get_recent_checklists needs a policy

This tool retrieves historical birding checklist data from the eBird API. It performs a read-only query operation with no side effects: it does not create, modify, delete, or execute any operations. The return of submission IDs enables follow-up queries but does not itself constitute a write or execute action.

From the tool's definition Tool description states it 'Get[s] recent checklists' and 'Returns subId for each checklist' — purely retrieving and querying data from eBird with no modification, deletion, or execution of external operations.

Questions about get_recent_checklists

What does the get_recent_checklists tool do? +

Get recent checklists submitted at a hotspot or in a region. Returns subId for each checklist so a specific one can be viewed with view_checklist. Use resolve_hotspot first if you only have a hotspot name. It is categorised as a Read tool in the Birding Buddy MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_recent_checklists? +

Register the Birding Buddy MCP server in PolicyLayer and add a rule for get_recent_checklists: 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.

What risk level is get_recent_checklists? +

get_recent_checklists is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_recent_checklists? +

Yes. Add a rate_limit block to the get_recent_checklists 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.

How do I block get_recent_checklists completely? +

Set action: deny in the PolicyLayer policy for get_recent_checklists. 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.

What MCP server provides get_recent_checklists? +

get_recent_checklists 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.