// SCAN REPORT

Waveapps

28 tools. 16 can modify or destroy data without limits.

6 destructive tools with no built-in limits. Policy required.

Last updated: 2 Jul 2026

16 can modify or destroy data

12 read-only

28 tools total

Community server · catalogue entry verified 02/07/2026

How to control Waveapps ↓

TOOL MAP

What Waveapps exposes to your agents

Read (12) Write / Execute (10) Destructive / Financial (6)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Waveapps tools

Financial · Critical wave_record_invoice_payment This tool directly commits a financial transaction by recording a payment against an invoice. Destructive · High wave_delete_customer This tool irreversibly removes customer records from the system. Destructive · High wave_delete_estimate This tool permanently removes estimate records from Wave Accounting. Destructive · High wave_delete_invoice Deleting invoices is a destructive action that permanently removes financial records and cannot be undone.

16 of Waveapps's 28 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Waveapps

PolicyLayer is an MCP gateway — it sits between your AI agents and Waveapps, and nothing reaches the server without passing your rules. These are the rules we recommend:

Block financial tools by default

{
  "wave_record_invoice_payment": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Deny destructive operations

{
  "wave_delete_customer": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "wave_approve_invoice": {
    "limits": [
      {
        "counter": "wave_approve_invoice_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "wave_get_business": {
    "limits": [
      {
        "counter": "wave_get_business_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Waveapps — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON WAVEAPPS →

Instant setup, no code required.

FULL CATALOGUE

All 28 Waveapps tools

FINANCIAL 1 tools

Financial wave_record_invoice_payment Records a manual payment (cash / cheque / bank transfer / etc.) against an approved invoice. REST POST

DESTRUCTIVE 5 tools

Destructive wave_delete_customer Deletes a customer. Wave warns this cannot be undone; the customer is removed from lists but historical invoic Destructive wave_delete_estimate Deletes an estimate by its Relay global ID. Only drafts and unsent estimates can be safely removed. Destructive wave_delete_invoice Deletes an invoice via REST Destructive wave_delete_invoice_payment Removes a recorded payment from an invoice. REST DELETE Destructive wave_delete_product Deletes a product via

EXECUTE 1 tools

Execute wave_send_invoice Sends an approved invoice to one or more recipients via Wave\

WRITE 9 tools

Write wave_approve_invoice Approves a draft invoice (status Write wave_create_customer Creates a new customer in Wave. Only Write wave_create_estimate Creates a new estimate. Pass the customer\ Write wave_create_invoice Creates an invoice via REST Write wave_create_product Creates a new product/service via Write wave_mark_invoice_sent Flips an approved invoice\ Write wave_update_estimate Patches an existing estimate. Pass the estimate\ Write wave_update_invoice Patches an invoice via REST Write wave_update_product Patches a product via

READ 12 tools

Read wave_get_business Fetches a single business by UUID, including profile/address/currency. Read wave_get_invoice Fetches a single invoice by ID, with customer/items/payments/taxes/attachments embedded. Read wave_get_invoice_settings Returns the workspace-wide invoice settings (numbering, terms, branding) used as defaults on new invoices. Read wave_get_product Fetches a single product by integer ID. Useful for double-checking the Read wave_list_accounts Lists active accounts in the chart of accounts. Use this to find the integer Read wave_list_bills Lists vendor bills (purchases) for a Wave business. GraphQL-backed; filter by vendor and date range. Read wave_list_businesses Returns every business (workspace) the current user has access to. Useful for picking a Read wave_list_customers Returns the customer roster for a Wave business. GraphQL-backed; includes addresses, phones, outstanding/overd Read wave_list_estimates Lists estimates for a Wave business. GraphQL returns three buckets at once (all / active / draft) — pick which Read wave_list_invoices Lists invoices for a Wave business. REST-backed ( Read wave_list_products Lists products/services for a Wave business via REST ( Read wave_list_receipts Lists receipt-capture transactions for a Wave business. GraphQL-backed; receipts are modelled as transactions

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Waveapps

Can an AI agent move money through the Waveapps MCP server? +

Yes. The Waveapps server exposes 1 financial tools including wave_record_invoice_payment. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

Can an AI agent delete data through the Waveapps MCP server? +

Yes. The Waveapps server exposes 5 destructive tools including wave_delete_customer, wave_delete_estimate, wave_delete_invoice. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Waveapps? +

The Waveapps server has 9 write tools including wave_approve_invoice, wave_create_customer, wave_create_estimate. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Waveapps.

How many tools does the Waveapps MCP server expose? +

28 tools across 4 categories: Destructive, Financial, Read, Write. 12 are read-only. 16 can modify, create, or delete data.

How do I enforce a policy on Waveapps? +

Register the Waveapps MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Waveapps tool call.

Deterministic rules across all 28 Waveapps tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON WAVEAPPS →

Instant setup, no code required.

28 Waveapps tools catalogued and risk-classified — across an index of 43,000+ MCP servers.