Perform complex queries with multiple filters for advanced bird data analysis.
AI agents call custom_bird_query to retrieve information from AviBase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool is described as performing queries with filters for analysis purposes, consistent with a Read operation. It sits alongside other clearly read-oriented tools (search_birds, get_bird_report, etc.) on a bird data server. However, the word 'custom' and 'complex queries' could imply some dynamic execution capability (similar to execute_jsonata_query on the same server), slightly lowering confidence.
From the tool's definition 'Perform complex queries with multiple filters for advanced bird data analysis' — querying/filtering existing bird data with no mention of modification or execution
Attacks that exploit this kind of access
Perform complex queries with multiple filters for advanced bird data analysis. It is categorised as a Read tool in the AviBase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AviBase MCP Server MCP server in PolicyLayer and add a rule for custom_bird_query: 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 AviBase MCP Server. Nothing to install.
custom_bird_query 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 custom_bird_query 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 custom_bird_query. 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.
custom_bird_query is provided by the AviBase MCP Server MCP server (kshayk/avibase-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 →