Change the Auto-Compound plan for a Dual Investment position to NONE, STANDARD, or ADVANCED using the position ID.
AI agents use registerBinanceChangeAutoCompoundStatus to create or update resources in Binance MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Binance MCP Server environment.
This tool modifies investment settings reversibly (auto-compound plans can be changed back), making it Write rather than Execute or Financial. However, given the financial domain context (Binance exchange, Dual Investment products), it receives high severity due to potential impact on yield/returns and the irreversible market consequences of plan changes during volatile periods.
From the tool's definition Tool description states it 'Change[s] the Auto-Compound plan' for a Dual Investment position, which modifies the configuration/settings of an existing investment position. The tool name contains 'register' and 'Change', indicating state modification.
Documented attack patterns abuse exactly the kind of access registerBinanceChangeAutoCompoundStatus gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Binance MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for registerBinanceChangeAutoCompoundStatus:
{
"version": "1",
"default": "deny",
"tools": {
"registerBinanceChangeAutoCompoundStatus": {
"limits": [
{
"counter": "registerbinancechangeautocompoundstatus_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}registerBinanceChangeAutoCompoundStatus 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.
Change the Auto-Compound plan for a Dual Investment position to NONE, STANDARD, or ADVANCED using the position ID. It is categorised as a Write tool in the Binance MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Binance MCP Server MCP server in PolicyLayer and add a rule for registerBinanceChangeAutoCompoundStatus: 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.
registerBinanceChangeAutoCompoundStatus 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 registerBinanceChangeAutoCompoundStatus 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 registerBinanceChangeAutoCompoundStatus. 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.
registerBinanceChangeAutoCompoundStatus is provided by the Binance MCP Server MCP server (termix-official/binance-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 160 Binance MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
160 Binance MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.