Legacy alias for search_by_common_name.
AI agents call search_by_vernacular_name to retrieve information from ITIS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a database query to search taxonomic information by vernacular (common) name. It retrieves data without modifying, deleting, or executing anything. No side effects are described. The severity is low because misuse of a taxonomic search cannot cause meaningful harm—an agent querying the wrong species name simply returns irrelevant results.
From the tool's definition Tool is a legacy search alias for 'search_by_common_name', which retrieves taxonomic data from ITIS database.
Attacks that exploit this kind of access
Legacy alias for search_by_common_name. It is categorised as a Read tool in the ITIS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ITIS MCP Server MCP server in PolicyLayer and add a rule for search_by_vernacular_name: 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 ITIS MCP Server. Nothing to install.
search_by_vernacular_name 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_by_vernacular_name 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_by_vernacular_name. 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_by_vernacular_name is provided by the ITIS MCP Server MCP server (knustx/itis-mcp-server). 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 →