create_appointment · Appointment Manager MCP Server MCP

WHAT IT DOES

What create_appointment does on Appointment Manager MCP Server

AI agents use create_appointment to create or update resources in Appointment Manager MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Appointment Manager MCP Server environment.

WHY IT NEEDS A POLICY

Why create_appointment needs a policy

This tool creates new records in the appointments database. Write operations are reversible (via delete or update), so it does not rise to Destructive severity. However, unauthorized appointment creation could disrupt business operations, block time slots, or enable social engineering attacks, warranting medium severity. Confidence is high because the intent is explicit in the name and description.

From the tool's definition Tool name 'create_appointment' and description 'Create a new appointment' indicate data creation. The server description confirms it 'supports creating, listing, updating, and deleting appointments' via a PostgreSQL backend, establishing this as a write…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_appointment Rate-limited

create_appointment stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_appointment": {
      "limits": [
        {
          "counter": "create_appointment_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Appointment Manager MCP Server, so you can run agents against it safely.

FAQ

Questions about create_appointment

What does the create_appointment tool do? +

Create a new appointment for a customer. It is categorised as a Write tool in the Appointment Manager MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_appointment? +

Register the Appointment Manager 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 Appointment Manager MCP Server. Nothing to install.

What risk level is create_appointment? +

create_appointment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_appointment? +

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.

How do I block create_appointment completely? +

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.

What MCP server provides create_appointment? +

create_appointment is provided by the Appointment Manager MCP Server MCP server (samuelr2112/mcp-project). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.