wave_create_estimate · Waveapps MCP: Risk & Policy

WHAT IT DOES

What wave_create_estimate does on Waveapps

AI agents use wave_create_estimate to create or update resources in Waveapps — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Waveapps environment.

WHY IT NEEDS A POLICY

Why wave_create_estimate needs a policy

Creating an estimate is a write operation that adds new financial data to the Wave Accounting system. While it creates a business document, estimates are typically non-binding and reversible (can be deleted or modified), distinguishing this from a destructive action. The incomplete description ('Pass the customer\') prevents full assessment of constraints, which slightly lowers confidence.

From the tool's definition Tool name is 'wave_create_estimate' and description states 'Creates a new estimate.' This is a reversible data creation operation in a financial accounting system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wave_create_estimate Rate-limited

wave_create_estimate 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": {
    "wave_create_estimate": {
      "limits": [
        {
          "counter": "wave_create_estimate_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 Waveapps, so you can run agents against it safely.

FAQ

Questions about wave_create_estimate

What does the wave_create_estimate tool do? +

Creates a new estimate. Pass the customer\. It is categorised as a Write tool in the Waveapps MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on wave_create_estimate? +

Register the Waveapps MCP server in PolicyLayer and add a rule for wave_create_estimate: 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 Waveapps. Nothing to install.

What risk level is wave_create_estimate? +

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

Can I rate-limit wave_create_estimate? +

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

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

wave_create_estimate is provided by the Waveapps MCP server (lunaparker/waveapps-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.