create-inspection · Zava Insurance MCP Server MCP

WHAT IT DOES

What create-inspection does on Zava Insurance MCP Server

AI agents use create-inspection to create or update resources in Zava Insurance MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zava Insurance MCP Server environment.

WHY IT NEEDS A POLICY

Why create-inspection needs a policy

This tool creates new inspection records in the insurance claims system, which is a reversible Write operation. While it doesn't delete or execute arbitrary code, it does create persistent data structures that could clutter the system or create fraudulent inspection records if misused by an agent.

From the tool's definition Tool name 'create-inspection' and description 'Creates a new inspection record' indicates data creation. The description notes auto-generation of ID and default status, confirming it modifies backend state by adding new records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create-inspection Rate-limited

create-inspection stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create-inspection": {
      "limits": [
        {
          "counter": "create-inspection_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Zava Insurance MCP Server, so you can run agents against it safely.

FAQ

Questions about create-inspection

What does the create-inspection tool do? +

Creates a new inspection record. Only claimNumber is required. ID is auto-generated, status defaults to. It is categorised as a Write tool in the Zava Insurance MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create-inspection? +

Register the Zava Insurance MCP Server MCP server in PolicyLayer and add a rule for create-inspection: 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 Zava Insurance MCP Server. Nothing to install.

What risk level is create-inspection? +

create-inspection is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create-inspection? +

Yes. Add a rate_limit block to the create-inspection 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.

How do I block create-inspection completely? +

Set action: deny in the PolicyLayer policy for create-inspection. 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.

What MCP server provides create-inspection? +

create-inspection is provided by the Zava Insurance MCP Server MCP server (rabwill/zava-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.