Create a new appointment on the operator
AI agents use create_appointment to create or update resources in ezyVet MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ezyVet MCP Server environment.
This tool creates a new appointment record in the veterinary practice management system. It is reversible (appointments can be cancelled/modified), so it is Write rather than Destructive. Severity is medium because creating bogus appointments could disrupt scheduling, waste staff time, or block legitimate bookings, but does not directly delete data, move money, or expose sensitive information.
From the tool's definition Tool name is 'create_appointment' and description states 'Create a new appointment' — creates new data (appointment record). Related tools include list_* (Read) and get_* (Read), confirming this is Write tier.
Attacks that exploit this kind of access
Create a new appointment on the operator. It is categorised as a Write tool in the ezyVet MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ezyVet MCP Server MCP server in PolicyLayer and add a rule for create_appointment: 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.
create_appointment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_appointment 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 create_appointment. 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.
create_appointment 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 →