Find likely duplicate transactions in a date range by grouping same date, amount, accounts, and item.
AI agents call whooing_duplicate_candidates to retrieve information from Whooing MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes existing financial data to identify potential duplicates without creating, modifying, or deleting entries. It is purely informational—a read operation on transaction history. While the server includes destructive tools like 'whooing_delete_entry' and write tools like 'whooing_add_entry' and 'whooing_bulk_add_entries', this specific tool only queries and presents findings.
From the tool's definition Tool name 'whooing_duplicate_candidates' and description 'Find likely duplicate transactions' indicates a query/analysis operation with no modification or deletion of data.
Attacks that exploit this kind of access
Find likely duplicate transactions in a date range by grouping same date, amount, accounts, and item. It is categorised as a Read tool in the Whooing MCP MCP Server, which means it retrieves data without modifying state.
Register the Whooing MCP server in PolicyLayer and add a rule for whooing_duplicate_candidates: 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 Whooing MCP. Nothing to install.
whooing_duplicate_candidates 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 whooing_duplicate_candidates 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 whooing_duplicate_candidates. 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.
whooing_duplicate_candidates is provided by the Whooing MCP server (jmjeong/whooing-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 →