APPROVAL-GATED: Calendly-style booking. Site-specific adapters not yet wired.
AI agents use book_appointment to create or update resources in Nexus Core — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nexus Core environment.
Booking an appointment creates a calendar reservation, which is a Write action (creates a new record/commitment). It could have financial implications if the booking involves paid services, but there's no explicit mention of payment processing. The 'APPROVAL-GATED' flag suggests some safeguard exists, but the underlying action is still creating a commitment on behalf of the user.
From the tool's definition book_appointment — 'Calendly-style booking'; 'APPROVAL-GATED'
Attacks that exploit this kind of access
APPROVAL-GATED: Calendly-style booking. Site-specific adapters not yet wired. It is categorised as a Write tool in the Nexus Core MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nexus Core 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 Nexus Core. 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 Nexus Core MCP server (noumenon-ai/nexus-core). 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 →