estimate_bitcoin_up_down_30m
Estimate BTC Up or Down probability for a fixed 30-minute window from caller-supplied prices.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/estimate-bitcoin-up-down-30m.md
What estimate_bitcoin_up_down_30m does on Delx Mcp A2a
AI agents call estimate_bitcoin_up_down_30m to retrieve information from Delx Mcp A2a without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
fee_bps | integer | — | Optional estimated entry fee in basis points. |
observations | array | Yes | Eight to 240 caller-supplied observations ordered oldest to newest. |
market_up_price | number | — | Optional caller-supplied UP share price for model-edge comparison. |
market_down_price | number | — | Optional caller-supplied DOWN share price for model-edge comparison. |
window_open_price | number | Yes | Caller-supplied opening price under the target venue's own rules. |
window_close_timestamp | integer | Yes | Unix close timestamp in seconds, later than the newest observation. |
Parameters from the server's own tool schema.
Why estimate_bitcoin_up_down_30m is rated Low
Even though estimate_bitcoin_up_down_30m only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs estimate_bitcoin_up_down_30m safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Mcp A2a, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For estimate_bitcoin_up_down_30m, this is the rule to start with:
estimate_bitcoin_up_down_30m 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 Delx Mcp A2a, apply this rule, and every estimate_bitcoin_up_down_30m call is checked against it from then on.
Questions about estimate_bitcoin_up_down_30m
Estimate BTC Up or Down probability for a fixed 30-minute window from caller-supplied prices. It is categorised as a Read tool in the Delx Mcp A2a MCP Server, which means it retrieves data without modifying state.
estimate_bitcoin_up_down_30m accepts 6 parameters: fee_bps, observations, market_up_price, market_down_price, window_open_price, window_close_timestamp. Required: observations, window_open_price, window_close_timestamp. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Mcp A2a MCP server in PolicyLayer and add a rule for estimate_bitcoin_up_down_30m: 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 Delx Mcp A2a. Nothing to install.
estimate_bitcoin_up_down_30m 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 estimate_bitcoin_up_down_30m 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 estimate_bitcoin_up_down_30m. 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.
estimate_bitcoin_up_down_30m is provided by the Delx Mcp A2a MCP server (https://api.delx.ai/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Mcp A2a, and thousands of servers like it.
This server
Across the catalogue