Register a DICT key on a BB account owned by the merchant. Some key types (email/phone) require BCB confirmation flows.
AI agents use register_dict_key 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 creates or modifies account configuration by registering a DICT (likely a payment identifier system) key, which is reversible (keys can be deactivated or removed). It does not move money, execute arbitrary code, or destroy data.
From the tool's definition Tool description states 'Register a DICT key on a BB account owned by the merchant' — register is a write operation that creates/adds a new DICT key entry to a merchant's account.
Documented attack patterns abuse exactly the kind of access register_dict_key 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 register_dict_key:
{
"version": "1",
"default": "deny",
"tools": {
"register_dict_key": {
"limits": [
{
"counter": "register_dict_key_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}register_dict_key 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.
Register a DICT key on a BB account owned by the merchant. Some key types (email/phone) require BCB confirmation flows. 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 register_dict_key: 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.
register_dict_key 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 register_dict_key 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 register_dict_key. 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.
register_dict_key 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.