AI agents use api_ultrade_wallet_add_key to create or update resources in BNB Chain MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BNB Chain MCP environment.
The tool creates/adds a new trading key, which is a reversible Write operation that modifies wallet configuration. However, it carries high severity because adding trading keys to a wallet could enable unauthorized trading or fund transfers if the AI agent is compromised or misuses the credential.
From the tool's definition Tool name 'api_ultrade_wallet_add_key' with description 'Add a trading key' indicates creation of new cryptographic credentials or trading permissions for a wallet.
Documented attack patterns abuse exactly the kind of access api_ultrade_wallet_add_key gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BNB Chain MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for api_ultrade_wallet_add_key:
{
"version": "1",
"default": "deny",
"tools": {
"api_ultrade_wallet_add_key": {
"limits": [
{
"counter": "api_ultrade_wallet_add_key_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}api_ultrade_wallet_add_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.
Add a trading key. It is categorised as a Write tool in the BNB Chain MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the BNB Chain MCP server in PolicyLayer and add a rule for api_ultrade_wallet_add_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 BNB Chain MCP. Nothing to install.
api_ultrade_wallet_add_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 api_ultrade_wallet_add_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 api_ultrade_wallet_add_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.
api_ultrade_wallet_add_key is provided by the BNB Chain MCP server (nirholas/bnbchain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 1240 BNB Chain MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
1240 BNB Chain MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.