Request confirmed sales appointments delivered to your calendar. Human SDRs handle outbound; you pay only per confirmed, BANT-qualified meeting. Use when the user wants to book meetings, generate pipeline, get demos, or set up sales calls — but does not want to do the outreach themselves. Returns...
AI agents use book_appointments to commit financial operations through LeadClaw MCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.
The tool description explicitly states a financial transaction occurs ('you pay only per confirmed meeting'), meaning invoking this tool commits the user to paying for each confirmed appointment generated. This is a financial obligation, making it the most severe applicable category.
From the tool's definition 'you pay only per confirmed, BANT-qualified meeting' — the tool explicitly involves a pay-per-meeting financial commitment triggered by booking confirmed sales appointments
Attacks that exploit this kind of access
Request confirmed sales appointments delivered to your calendar. Human SDRs handle outbound; you pay only per confirmed, BANT-qualified meeting. Use when the user wants to book meetings, generate pipeline, get demos, or set up sales calls — but does not want to do the outreach themselves. Returns a request_id; poll check_status to see confirmed appointments populate. It is categorised as a Financial tool in the LeadClaw MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the LeadClaw MCP server in PolicyLayer and add a rule for book_appointments: 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 LeadClaw MCP. Nothing to install.
book_appointments is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the book_appointments 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_appointments. 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_appointments is provided by the LeadClaw MCP server (no39pikko/leadclaw-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 →