fishwatch_species_detail
Get detailed info about a specific fish species from NOAA FishWatch.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/fishwatch-species-detail.md
What fishwatch_species_detail does on UnClick
AI agents call fishwatch_species_detail to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Species name with hyphens (e.g. atlantic-salmon, pacific-cod). |
Parameters from the server's own tool schema.
Why fishwatch_species_detail is rated Low
This tool retrieves informational data about fish species from a public NOAA database. It has no side effects, does not modify or delete data, does not execute code or scripts, and poses no financial risk. It is a simple read-only query operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name contains 'detail' and description states 'Get detailed info about a specific fish species from NOAA FishWatch' - a straightforward data retrieval operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
The rule that runs fishwatch_species_detail safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fishwatch_species_detail, this is the rule to start with:
fishwatch_species_detail is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every fishwatch_species_detail call is checked against it from then on.
Questions about fishwatch_species_detail
Get detailed info about a specific fish species from NOAA FishWatch. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
fishwatch_species_detail accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for fishwatch_species_detail: 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 UnClick. Nothing to install.
fishwatch_species_detail 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 fishwatch_species_detail 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 fishwatch_species_detail. 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.
fishwatch_species_detail is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue