Get ecological information for a species
AI agents call get_ecology to retrieve information from MCP FishBase Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves ecological data about fish species from FishBase. It performs a read-only query with no side effects, no code execution, no data modification, and no destructive operations. The narrow scope (ecological information for a single species) and informational nature of the data mean the blast radius of misuse is minimal.
From the tool's definition Tool name 'get_ecology' and description 'Get ecological information for a species' indicate data retrieval with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get ecological information for a species. It is categorised as a Read tool in the MCP FishBase Server MCP Server, which means it retrieves data without modifying state.
Register the MCP FishBase Server MCP server in PolicyLayer and add a rule for get_ecology: 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 MCP FishBase Server. Nothing to install.
get_ecology 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 get_ecology 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 get_ecology. 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.
get_ecology is provided by the MCP FishBase Server MCP server (lundgrenalex/mcp-fishbase). 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 →