Add a value to the Konduto allowlist (trusted). Future orders matching the value are auto-approved without full ML scoring. Use sparingly — allowlist overrides fraud signals.
AI agents use add_to_allowlist to create or update resources in Mcp Ap2 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Ap2 environment.
This tool writes/modifies a fraud detection configuration by adding entries to an allowlist, causing future orders to bypass ML fraud scoring. While it doesn't move money directly, it persistently modifies a security control that governs financial transaction approvals.
From the tool's definition 'Add a value to the Konduto allowlist (trusted). Future orders matching the value are auto-approved without full ML scoring. allowlist overrides fraud signals.'
Documented attack patterns abuse exactly the kind of access add_to_allowlist 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 add_to_allowlist:
{
"version": "1",
"default": "deny",
"tools": {
"add_to_allowlist": {
"limits": [
{
"counter": "add_to_allowlist_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} add_to_allowlist stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add a value to the Konduto allowlist (trusted). Future orders matching the value are auto-approved without full ML scoring. Use sparingly — allowlist overrides fraud signals. It is categorised as a Write tool in the Mcp Ap2 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for add_to_allowlist: 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.
add_to_allowlist is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_to_allowlist 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 add_to_allowlist. 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.
add_to_allowlist 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.