Search for species by common name or partial scientific name
AI agents call search_species 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 species information from a marine biology database. Search and lookup operations are inherently read-only with no side effects. There is no indication of data modification, code execution, deletion, or financial impact. The low severity reflects minimal risk even if misused—a search query cannot harm data or systems.
From the tool's definition Tool description states 'Search for species' which is a retrieval operation. Server description indicates it 'Provides access to FishBase marine biology data' and enables 'species name validation.' The tool performs queries against read-only reference data…
Attacks that exploit this kind of access
Search for species by common name or partial scientific name. 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 search_species: 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.
search_species 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 search_species 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 search_species. 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.
search_species 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 →