bn_keepalive_listen_key · Node2flow/binance MCP

WHAT IT DOES

What bn_keepalive_listen_key does on Node2flow/binance

AI agents use bn_keepalive_listen_key to create or update resources in Node2flow/binance — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Node2flow/binance environment.

WHY IT NEEDS A POLICY

Why bn_keepalive_listen_key needs a policy

This tool updates/extends the validity of an existing listen key, which is a reversible modification (Write). It doesn't retrieve data, execute code, destroy anything, or involve finances. Severity is low since misuse only extends a key's lifetime, with minimal blast radius.

From the tool's definition Keepalive a listen key to extend its validity by 60 minutes. Should be called periodically to prevent expiration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bn_keepalive_listen_key Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bn_keepalive_listen_key": {
      "limits": [
        {
          "counter": "bn_keepalive_listen_key_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Node2flow/binance, so you can run agents against it safely.

FAQ

Questions about bn_keepalive_listen_key

What does the bn_keepalive_listen_key tool do? +

Keepalive a listen key to extend its validity by 60 minutes. Should be called periodically to prevent expiration. It is categorised as a Write tool in the Node2flow/binance MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on bn_keepalive_listen_key? +

Register the Node2flow/binance MCP server in PolicyLayer and add a rule for bn_keepalive_listen_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 Node2flow/binance. Nothing to install.

What risk level is bn_keepalive_listen_key? +

bn_keepalive_listen_key is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit bn_keepalive_listen_key? +

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

How do I block bn_keepalive_listen_key completely? +

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

What MCP server provides bn_keepalive_listen_key? +

bn_keepalive_listen_key is provided by the Node2flow/binance MCP server (node2flow-th/binance-mcp-community). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.