Check the progress of a LeadClaw appointment request. Returns current phase (processing / matching / in_progress / completed) and any confirmed appointments so far. Call this after book_appointments and re-poll as needed until status is completed.
AI agents call check_status 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.
check_status retrieves and queries appointment request status information without creating, modifying, deleting, or executing any operations. This is a read-only retrieval of state information, the lowest risk category. Confidence is high because the description is explicit and unambiguous about its read-only nature.
From the tool's definition Tool description explicitly states it 'Check[s] the progress' and 'Returns current phase...and any confirmed appointments' — purely informational queries with no data modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Check the progress of a LeadClaw appointment request. Returns current phase (processing / matching / in_progress / completed) and any confirmed appointments so far. Call this after book_appointments and re-poll as needed until status is completed. 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 check_status: 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.
check_status 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 check_status 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 check_status. 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.
check_status 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 →