Get morphological and physiological data for a species
AI agents call get_morphology 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 morphological and physiological data without creating, modifying, deleting, or executing any operations. It is a straightforward data query operation similar to other sibling tools like get_species, get_ecology, and get_distribution on the same server. No side effects or state changes occur.
From the tool's definition Tool name 'get_morphology' and description 'Get morphological and physiological data for a species' indicate data retrieval with no modification capabilities. The verb 'Get' and context of a FishBase biology database confirm read-only querying.
Attacks that exploit this kind of access
Get morphological and physiological data 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_morphology: 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_morphology 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_morphology 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_morphology. 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_morphology 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 →