book_demo
Book a free Aivonic discovery call at a specific slot for a real person. start_iso must be an ISO-8601 start time returned by check_availability. Provide the prospect's real name and email; a calendar invite is sent to them. Returns booking confirmation or an error.
This record as markdown: /tools/ai-aivonic-mcp/book-demo.md
What book_demo does on Mcp
AI agents invoke book_demo to trigger actions in Mcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | |
email | string | Yes | |
notes | string | — | |
start_iso | string | Yes | |
timezone_name | string | — |
Parameters from the server's own tool schema.
Why book_demo is rated High
book_demo triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs book_demo safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For book_demo, this is the rule to start with:
book_demo stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every book_demo call is checked against it from then on.
Questions about book_demo
Book a free Aivonic discovery call at a specific slot for a real person. start_iso must be an ISO-8601 start time returned by check_availability. Provide the prospect's real name and email; a calendar invite is sent to them. Returns booking confirmation or an error. It is categorised as a Execute tool in the Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
book_demo accepts 5 parameters: name, email, notes, start_iso, timezone_name. Required: name, email, start_iso. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for book_demo: 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 Mcp. Nothing to install.
book_demo is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the book_demo 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_demo. 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_demo is provided by the MCP server (https://mcp.aivonic.ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue