Get RWA trading config: supported stablecoins, slippage, amount limits, gas info.
AI agents call rwa_config to retrieve information from Bitget Wallet MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns static or semi-static configuration information about RWA (Real-World Asset) trading parameters. It has no side effects, does not modify data, execute code, delete records, or commit financial transactions. It is a pure read operation consistent with other query tools on this server (balance, batch_token_info, coin_market_info, get_token_list, etc.).
From the tool's definition Tool description explicitly states "Get RWA trading config" — a retrieval operation that queries configuration data (supported stablecoins, slippage, amount limits, gas info). No modification, execution, deletion, or financial transaction occurs.
Documented attack patterns abuse exactly the kind of access rwa_config gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bitget Wallet MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for rwa_config:
{
"version": "1",
"default": "deny",
"tools": {
"rwa_config": {}
}
}rwa_config 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.
Get RWA trading config: supported stablecoins, slippage, amount limits, gas info. It is categorised as a Read tool in the Bitget Wallet MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bitget Wallet MCP Server MCP server in PolicyLayer and add a rule for rwa_config: 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 Wallet MCP Server. Nothing to install.
rwa_config 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 rwa_config 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 rwa_config. 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.
rwa_config is provided by the Bitget Wallet MCP Server MCP server (bitget-wallet-ai-lab/bitget-wallet-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bitget Wallet MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
39 Bitget Wallet MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.