Low Risk

market_24hr

OKX crypto exchange 24-hour rolling stats for an instrument: open, high, low, last, volume, vol-ccy. Use for daily summary on OKX.

Part of the Okx server.

market_24hr is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE OKX →

Free to start. No card required.

AI agents call market_24hr to retrieve information from Okx without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though market_24hr only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "market_24hr": {}
  }
}

See the full Okx policy for all 33 tools.

Get this rule live on your own Okx server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY OKX →

View all 33 tools →

These attack patterns abuse exactly the kind of access market_24hr gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so market_24hr only ever does what you allow.

SECURE OKX →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the market_24hr tool do? +

OKX crypto exchange 24-hour rolling stats for an instrument: open, high, low, last, volume, vol-ccy. Use for daily summary on OKX.. It is categorised as a Read tool in the Okx MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on market_24hr? +

Register the Okx MCP server in PolicyLayer and add a rule for market_24hr: 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 Okx. Nothing to install.

What risk level is market_24hr? +

market_24hr is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit market_24hr? +

Yes. Add a rate_limit block to the market_24hr 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.

How do I block market_24hr completely? +

Set action: deny in the PolicyLayer policy for market_24hr. 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.

What MCP server provides market_24hr? +

market_24hr is provided by the Okx MCP server (https://gateway.pipeworx.io/okx/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Okx tool call.

Deterministic rules across all 33 Okx tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.