Check whether a value is currently on the Konduto reviewlist. Konduto
AI agents call query_reviewlist to retrieve information from Mcp Ap2 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 lookup against a review list to determine if a value is flagged or present. It retrieves information (fraud risk assessment data) without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal — an attacker could only learn whether specific values are flagged, not cause financial transactions, data loss, or unintended modifications.
From the tool's definition Tool description states "Check whether a value is currently on the Konduto reviewlist" — a query operation that retrieves status information without modifying data.
Documented attack patterns abuse exactly the kind of access query_reviewlist gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for query_reviewlist:
{
"version": "1",
"default": "deny",
"tools": {
"query_reviewlist": {}
}
} query_reviewlist 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.
Check whether a value is currently on the Konduto reviewlist. Konduto. It is categorised as a Read tool in the Mcp Ap2 MCP Server, which means it retrieves data without modifying state.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for query_reviewlist: 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 Mcp Ap2. Nothing to install.
query_reviewlist 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 query_reviewlist 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 query_reviewlist. 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.
query_reviewlist is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, 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.
1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.