Pull full briefing on a specific confirmed appointment: contact info, company context, full BANT breakdown, SDR call notes, and meeting link. Use when the user wants to prep for a specific meeting.
AI agents call get_appointment_details to retrieve information from LeadClaw MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure data retrieval operation. It queries and returns appointment details without any side effects, modifications, or external executions. The narrow scope (accessing a specific confirmed appointment's pre-existing briefing data) and read-only nature warrant 'low' severity—misuse would expose sales information but cannot trigger financial transactions, delete data, or execute code.
From the tool's definition Tool pulls and retrieves data ('Pull full briefing', 'contact info', 'company context', 'BANT breakdown', 'SDR call notes', 'meeting link') with no indication of modification, deletion, or execution of external actions.
Attacks that exploit this kind of access
Pull full briefing on a specific confirmed appointment: contact info, company context, full BANT breakdown, SDR call notes, and meeting link. Use when the user wants to prep for a specific meeting. It is categorised as a Read tool in the LeadClaw MCP MCP Server, which means it retrieves data without modifying state.
Register the LeadClaw MCP server in PolicyLayer and add a rule for get_appointment_details: 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.
get_appointment_details is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_appointment_details 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 get_appointment_details. 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.
get_appointment_details 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 →