update-purchase-order · Zava Insurance MCP Server MCP

WHAT IT DOES

What update-purchase-order does on Zava Insurance MCP Server

AI agents use update-purchase-order 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 update-purchase-order needs a policy

This tool modifies purchase order records reversibly (status can be changed again), making it Write rather than Destructive. However, severity is high because purchase order status updates directly impact financial workflows—approving a purchase order commits the insurance company to payment obligations with contractors. While not a direct financial transaction, it is a prerequisite action that triggers payment.

From the tool's definition Tool name 'update-purchase-order' and description 'Updates a purchase order status' indicate modification of existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update-purchase-order Rate-limited

update-purchase-order 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": {
    "update-purchase-order": {
      "limits": [
        {
          "counter": "update-purchase-order_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 update-purchase-order

What does the update-purchase-order tool do? +

Updates a purchase order status (e.g. approve, reject, complete). 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 update-purchase-order? +

Register the Zava Insurance MCP Server MCP server in PolicyLayer and add a rule for update-purchase-order: 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 update-purchase-order? +

update-purchase-order is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update-purchase-order? +

Yes. Add a rate_limit block to the update-purchase-order 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 update-purchase-order completely? +

Set action: deny in the PolicyLayer policy for update-purchase-order. 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 update-purchase-order? +

update-purchase-order 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.