AI agents call wave_list_customers to retrieve information from Waveapps without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries financial data—customer records, contact information, and account balances—without creating, modifying, or deleting anything. It has no side effects. While the data returned is sensitive (financial amounts, contact details), the tool itself performs only a Read operation with blast radius limited to data exposure rather than system modification.
From the tool's definition Tool name 'wave_list_customers' and description 'Returns the customer roster' indicate a retrieval operation with no modifications. GraphQL-backed query that only fetches existing data (addresses, phones, amounts, contacts, cards).
Attacks that exploit this kind of access
Returns the customer roster for a Wave business. GraphQL-backed; includes addresses, phones, outstanding/overdue amounts, additional contacts, saved cards. It is categorised as a Read tool in the Waveapps MCP Server, which means it retrieves data without modifying state.
Register the Waveapps MCP server in PolicyLayer and add a rule for wave_list_customers: 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.
wave_list_customers is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the wave_list_customers 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.
Set action: deny in the PolicyLayer policy for wave_list_customers. 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.
wave_list_customers 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →