book_appointment
Lead-gen/CRM: record an appointment in your pipeline (a DB row — no external calendar). Owner-gated. Returns {ok, appointment_id}.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/book-appointment.md
What book_appointment does on Gateway
AI agents use book_appointment to create or update resources in Gateway, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gateway environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | |
handle | string | Yes | |
secret | string | — | |
lead_id | integer | — | link to a captured lead, optional |
service | string | — | |
datetime | string | Yes | ISO datetime, e.g. 2026-07-10T14:00 |
session_id | string | — |
Parameters from the server's own tool schema.
Why book_appointment is rated Medium
The tool creates a new database record (a DB row) for an appointment in a CRM/lead-gen pipeline. This is a reversible write operation — it creates data but does not delete or overwrite anything, trigger code execution, or move money. Owner-gated access slightly reduces misuse risk, but an AI agent could still spam or pollute the pipeline with bogus appointments, warranting medium severity.
From the tool's definition record an appointment in your pipeline (a DB row — no external calendar)
Risk signalsHandles credentials or secrets (secret)
Attacks that exploit this kind of access
The rule that runs book_appointment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For book_appointment, this is the rule to start with:
book_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every book_appointment call is checked against it from then on.
Questions about book_appointment
Lead-gen/CRM: record an appointment in your pipeline (a DB row — no external calendar). Owner-gated. Returns {ok, appointment_id}. It is categorised as a Write tool in the Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
book_appointment accepts 7 parameters: name, handle, secret, lead_id, service, datetime, session_id. Required: handle, datetime. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for book_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 Gateway. Nothing to install.
book_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 book_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 book_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.
book_appointment is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue