Find an eBird hotspot by common name. Returns locId, full name, coordinates, and a direct eBird URL. If multiple matches are found, returns them sorted by distance from your location.
AI agents call resolve_hotspot 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 only retrieves and returns information about eBird hotspots — no data is created, modified, or deleted. It is a straightforward lookup/search operation with no side effects.
From the tool's definition Find an eBird hotspot by common name. Returns locId, full name, coordinates, and a direct eBird URL.
Attacks that exploit this kind of access
Find an eBird hotspot by common name. Returns locId, full name, coordinates, and a direct eBird URL. If multiple matches are found, returns them sorted by distance from your location. 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 resolve_hotspot: 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.
resolve_hotspot 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 resolve_hotspot 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 resolve_hotspot. 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.
resolve_hotspot 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 →