Low Risk

dex_market

DexScreener DEX data: search pairs/tokens, get specific pair info, token details by address, trending token boosts.

Risk signalsAccepts freeform code/query input (query)

Part of the Bitget server.

dex_market 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 BITGET →

Free to start. No card required.

AI agents call dex_market to retrieve information from Bitget 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 dex_market 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": {
    "dex_market": {}
  }
}

See the full Bitget policy for all 19 tools.

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

ENFORCE ON MY BITGET →

View all 19 tools →

These attack patterns abuse exactly the kind of access dex_market 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 dex_market only ever does what you allow.

SECURE BITGET →

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

What does the dex_market tool do? +

DexScreener DEX data: search pairs/tokens, get specific pair info, token details by address, trending token boosts.. It is categorised as a Read tool in the Bitget MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on dex_market? +

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

What risk level is dex_market? +

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

Can I rate-limit dex_market? +

Yes. Add a rate_limit block to the dex_market 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 dex_market completely? +

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

dex_market is provided by the Bitget MCP server (bitget-ai/bitget-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Bitget tool call.

Deterministic rules across all 19 Bitget 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.