ebird_recent_observations
Get recent bird observations from eBird.
This record as markdown: /tools/creativelead-unclick/ebird-recent-observations.md
What ebird_recent_observations does on UnClick
AI agents call ebird_recent_observations to retrieve information from UnClick 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 |
|---|---|---|---|
back | number | — | Days back (max 30) |
api_key | string | — | |
maxResults | number | — | |
regionCode | string | — | e.g. AU-VIC |
Parameters from the server's own tool schema.
Why ebird_recent_observations is rated Low
This tool queries and retrieves observational data from eBird, a read-only operation. There are no side effects, no data modification, no code execution, and no financial implications. The blast radius of misuse is minimal—an agent could at worst retrieve irrelevant or excessive bird observation data, which poses negligible risk.
From the tool's definition Tool description states 'Get recent bird observations from eBird' — a retrieval operation with no modification, deletion, or execution of external actions.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs ebird_recent_observations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ebird_recent_observations, this is the rule to start with:
ebird_recent_observations 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 UnClick, apply this rule, and every ebird_recent_observations call is checked against it from then on.
Questions about ebird_recent_observations
Get recent bird observations from eBird. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
ebird_recent_observations accepts 4 parameters: back, api_key, maxResults, regionCode. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for ebird_recent_observations: 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 UnClick. Nothing to install.
ebird_recent_observations 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 ebird_recent_observations 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 ebird_recent_observations. 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.
ebird_recent_observations is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue