BinanceSubAccountGetApiKeyIpRestriction
Get IP restriction for a sub-account API key.
This record as markdown: /tools/nirholas-binance-mcp/binancesubaccountgetapikeyiprestriction.md
What BinanceSubAccountGetApiKeyIpRestriction does on Binance MCP Server
AI agents call BinanceSubAccountGetApiKeyIpRestriction to retrieve information from Binance MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why BinanceSubAccountGetApiKeyIpRestriction is rated Low
This tool retrieves existing IP restriction settings for a sub-account API key. It is a read-only query operation that does not create, modify, delete, or execute any financial transactions. However, severity is elevated to medium because the data retrieved (IP restriction rules) could be sensitive information that, if exposed to an unauthorized actor, might facilitate social engineering or attacks on sub-accounts.
From the tool's definition Tool name includes 'Get' and description states 'Get IP restriction' — a retrieval operation with no modification or execution of trades/transfers. It queries configuration data for a sub-account API key.
Attacks that exploit this kind of access
The rule that runs BinanceSubAccountGetApiKeyIpRestriction safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Binance MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For BinanceSubAccountGetApiKeyIpRestriction, this is the rule to start with:
BinanceSubAccountGetApiKeyIpRestriction is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Binance MCP Server, apply this rule, and every BinanceSubAccountGetApiKeyIpRestriction call is checked against it from then on.
Questions about BinanceSubAccountGetApiKeyIpRestriction
Get IP restriction for a sub-account API key. It is categorised as a Read tool in the Binance MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Binance MCP Server MCP server in PolicyLayer and add a rule for BinanceSubAccountGetApiKeyIpRestriction: 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 Binance MCP Server. Nothing to install.
BinanceSubAccountGetApiKeyIpRestriction is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the BinanceSubAccountGetApiKeyIpRestriction 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 BinanceSubAccountGetApiKeyIpRestriction. 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.
BinanceSubAccountGetApiKeyIpRestriction is provided by the Binance MCP Server MCP server (nirholas/binance-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Binance MCP Server, and thousands of servers like it.
This server
Across the catalogue