Critical Risk →

remove_from_reviewlist

Remove a value from the Konduto reviewlist. Future orders matching the value will be scored normally instead of being forced into review.

How to control remove_from_reviewlist ↓

What remove_from_reviewlist does on Mcp Ap2

AI agents call remove_from_reviewlist to permanently remove resources in Mcp Ap2 — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why remove_from_reviewlist needs a policy

Removing an entry from a fraud review list is an irreversible security control change. It alters the fraud screening pipeline such that previously flagged values bypass mandatory review, which cannot be undone for orders already processed after removal. This has a high blast radius as it could allow fraudulent transactions to go undetected.

From the tool's definition 'Remove a value from the Konduto reviewlist' — permanently removes an entry, meaning future orders matching that value will no longer be forced into review

Documented attack patterns abuse exactly the kind of access remove_from_reviewlist gives an agent:

How to control remove_from_reviewlist

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 remove_from_reviewlist:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_from_reviewlist"
  ]
}

remove_from_reviewlist disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Mcp Ap2 — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about remove_from_reviewlist

What does the remove_from_reviewlist tool do? +

Remove a value from the Konduto reviewlist. Future orders matching the value will be scored normally instead of being forced into review. It is categorised as a Destructive tool in the Mcp Ap2 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_from_reviewlist? +

Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for remove_from_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.

What risk level is remove_from_reviewlist? +

remove_from_reviewlist is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_from_reviewlist? +

Yes. Add a rate_limit block to the remove_from_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.

How do I block remove_from_reviewlist completely? +

Set action: deny in the PolicyLayer policy for remove_from_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.

What MCP server provides remove_from_reviewlist? +

remove_from_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.

Enforce policy on every Mcp Ap2 tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.