Calculate the Double Exponential Moving Average (DEMA) for a given trading pair using Binance OHLCV data
How to control calculate_double_exponential_moving_average ↓
AI agents call calculate_double_exponential_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 is a pure analytical/computational tool that reads historical market data and derives a technical indicator. It has no side effects on blockchain state, user wallets, balances, or storage. No data is created, modified, deleted, or destroyed. No financial transactions are executed.
From the tool's definition Tool calculates a technical analysis metric (DEMA) on historical price data from Binance OHLCV. The verb 'Calculate' and 'for a given trading pair' indicates data retrieval and computation without modification, deletion, or execution of transactions.
Documented attack patterns abuse exactly the kind of access calculate_double_exponential_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_double_exponential_moving_average:
{
"version": "1",
"default": "deny",
"tools": {
"calculate_double_exponential_moving_average": {}
}
}calculate_double_exponential_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 Double Exponential Moving Average (DEMA) 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_double_exponential_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_double_exponential_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_double_exponential_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_double_exponential_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_double_exponential_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.