Check the status of an existing Lemonade insurance claim
AI agents call check_claim_status to retrieve information from Lemonade MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query to retrieve the current status of an insurance claim. It does not create, modify, delete, or execute any operations—it only fetches and displays information. The severity is low because checking claim status poses minimal risk; it cannot be misused to cause financial harm, delete data, or execute unintended operations.
From the tool's definition Tool name 'check_claim_status' and description 'Check the status of an existing Lemonade insurance claim' indicate retrieval of claim status information with no modification or execution of operations.
Attacks that exploit this kind of access
Check the status of an existing Lemonade insurance claim. It is categorised as a Read tool in the Lemonade MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lemonade MCP Server MCP server in PolicyLayer and add a rule for check_claim_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 Lemonade MCP Server. Nothing to install.
check_claim_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_claim_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_claim_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_claim_status is provided by the Lemonade MCP Server MCP server (markswendsen-code/mcp-lemonade). 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 →