Get Binance server time (millisecond timestamp). Use to check connectivity and sync timestamps for signed requests.
AI agents call bn_server_time to retrieve information from Node2flow/binance without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a single data point (server timestamp) from Binance without modifying any state, creating orders, executing trades, or transferring funds. It is a straightforward Read operation with minimal blast radius if misused by an agent—at worst it could be called excessively, but it poses no risk to user accounts, balances, or data integrity.
From the tool's definition Tool name 'bn_server_time' and description 'Get Binance server time (millisecond timestamp)' indicate a simple query operation that retrieves data with no side effects. The purpose is to 'check connectivity and sync timestamps' — read-only operations.
Attacks that exploit this kind of access
Get Binance server time (millisecond timestamp). Use to check connectivity and sync timestamps for signed requests. It is categorised as a Read tool in the Node2flow/binance MCP Server, which means it retrieves data without modifying state.
Register the Node2flow/binance MCP server in PolicyLayer and add a rule for bn_server_time: 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.
bn_server_time 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 bn_server_time 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 bn_server_time. 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.
bn_server_time 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →