verify_sighting

Cross-reference an eBird species sighting against iNaturalist photo-verified observations nearby. Returns confidence level and count of research-grade (photo-verified) reports.

Server Birding Planner minikdj/ebird-birding-planner
Category Read
Risk class Low
Parameters 00 required

What verify_sighting does on Birding Planner

AI agents call verify_sighting to retrieve information from Birding Planner without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why verify_sighting needs a policy

This tool retrieves and queries data from iNaturalist to validate or assess eBird sightings. It has no side effects—it neither creates, modifies, deletes, nor executes any operations. The returned confidence level and report count are derived from existing data. This is a pure read operation.

From the tool's definition Tool performs a cross-reference query ('Cross-reference') against existing photo-verified observations, returning a confidence level and count of reports. No modification, deletion, or execution of external actions occurs.

Questions about verify_sighting

What does the verify_sighting tool do? +

Cross-reference an eBird species sighting against iNaturalist photo-verified observations nearby. Returns confidence level and count of research-grade (photo-verified) reports. It is categorised as a Read tool in the Birding Planner MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on verify_sighting? +

Register the Birding Planner MCP server in PolicyLayer and add a rule for verify_sighting: 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 Planner. Nothing to install.

What risk level is verify_sighting? +

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

Can I rate-limit verify_sighting? +

Yes. Add a rate_limit block to the verify_sighting 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 verify_sighting completely? +

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

verify_sighting is provided by the Birding Planner MCP server (minikdj/ebird-birding-planner). 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.