wave_send_invoice · Waveapps MCP: Risk & Policy

WHAT IT DOES

What wave_send_invoice does on Waveapps

AI agents invoke wave_send_invoice to trigger actions in Waveapps. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why wave_send_invoice needs a policy

This tool triggers an external communication action — sending an invoice via email to recipients. It is not purely a write/data-modification operation; it executes an external operation (email delivery) with real-world effects that cannot be easily undone. Misuse could result in sending incorrect invoices to customers, causing confusion or financial disputes.

From the tool's definition 'Sends an approved invoice to one or more recipients via Wave'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wave_send_invoice Rate-limited

wave_send_invoice stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_send_invoice": {
      "limits": [
        {
          "counter": "wave_send_invoice_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_send_invoice

What does the wave_send_invoice tool do? +

Sends an approved invoice to one or more recipients via Wave\. It is categorised as a Execute tool in the Waveapps MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on wave_send_invoice? +

Register the Waveapps MCP server in PolicyLayer and add a rule for wave_send_invoice: 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_send_invoice? +

wave_send_invoice is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit wave_send_invoice? +

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

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

wave_send_invoice 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.