Search for an existing vendor in Wave (vendors must be created manually in Wave
AI agents call search_vendor to retrieve information from Wave Accounting MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only search operation to locate vendor records. The description explicitly notes that vendors must be created manually in Wave, confirming this tool only retrieves existing data. No data is modified, created, or deleted.
From the tool's definition The tool description states it 'Search[es] for an existing vendor in Wave' with no mention of creation, modification, or deletion. This is a query operation that retrieves vendor information without side effects.
Documented attack patterns abuse exactly the kind of access search_vendor gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Wave Accounting MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_vendor:
{
"version": "1",
"default": "deny",
"tools": {
"search_vendor": {}
}
} search_vendor is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search for an existing vendor in Wave (vendors must be created manually in Wave. It is categorised as a Read tool in the Wave Accounting MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Wave Accounting MCP Server MCP server in PolicyLayer and add a rule for search_vendor: 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 Wave Accounting MCP Server. Nothing to install.
search_vendor 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 search_vendor 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 search_vendor. 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.
search_vendor is provided by the Wave Accounting MCP Server MCP server (vinnividivicci/wave_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Wave Accounting MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 Wave Accounting MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.