Get full metadata for a single animal by id.
AI agents call get_animal to retrieve information from ezyVet MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves veterinary practice data about an animal without modifying, deleting, or executing operations. It is a straightforward data lookup operation analogous to a GET request in REST APIs. The classification aligns with the Read category (retrieves or queries data; no side effects). Severity is low because misuse would only expose data visibility, not cause irreversible harm or financial impact.
From the tool's definition Tool name 'get_animal' and description 'Get full metadata for a single animal by id' indicate a retrieval operation with no side effects. The verb 'Get' and the scope (single animal by id) confirm read-only semantics.
Attacks that exploit this kind of access
Get full metadata for a single animal by id. It is categorised as a Read tool in the ezyVet MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ezyVet MCP Server MCP server in PolicyLayer and add a rule for get_animal: 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 ezyVet MCP Server. Nothing to install.
get_animal 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_animal 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_animal. 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_animal is provided by the ezyVet MCP Server MCP server (nobanks/ezyvet-mcp). 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 →