Calculate the Triangular Moving Average (TRIMA) for a given trading pair using Binance OHLCV data
AI agents call calculate_triangular_moving_average to retrieve information from BNB Chain MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and processes market data to compute a standard technical indicator. It has no side effects, does not execute trades, does not access wallets, and does not modify any blockchain state. It is a pure Read operation that returns calculated analytics based on input data.
From the tool's definition The tool calculates a technical analysis metric (Triangular Moving Average) from historical OHLCV data without modifying, deleting, or executing any transactions or code.
Documented attack patterns abuse exactly the kind of access calculate_triangular_moving_average 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 calculate_triangular_moving_average:
{
"version": "1",
"default": "deny",
"tools": {
"calculate_triangular_moving_average": {}
}
}calculate_triangular_moving_average is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Calculate the Triangular Moving Average (TRIMA) for a given trading pair using Binance OHLCV data. It is categorised as a Read tool in the BNB Chain MCP MCP Server, which means it retrieves data without modifying state.
Register the BNB Chain MCP server in PolicyLayer and add a rule for calculate_triangular_moving_average: 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.
calculate_triangular_moving_average 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 calculate_triangular_moving_average 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 calculate_triangular_moving_average. 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.
calculate_triangular_moving_average 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.