Inventory contacts (pet owners + suppliers + staff).
AI agents call list_contacts 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 and enumerates contact records without creating, modifying, or deleting data. It has no side effects beyond data retrieval. The blast radius of misuse is limited to potential exposure of contact information, which is a read-level risk. This falls clearly into the Read category as a data retrieval operation with no reversible or irreversible modifications possible.
From the tool's definition Tool name 'list_contacts' and description 'Inventory contacts' indicate a retrieval/query operation with no modification capability.
Attacks that exploit this kind of access
Inventory contacts (pet owners + suppliers + staff). 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 list_contacts: 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.
list_contacts 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 list_contacts 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 list_contacts. 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.
list_contacts 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 →