Low Risk

query_account_asset

查询账户资产

How to control query_account_asset ↓

AI agents call query_account_asset to retrieve information from QMT-MCP-Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool queries account asset information, retrieving financial data about holdings, balances, or positions. It performs no modifications, deletions, or financial transactions. While the data is sensitive (financial information), the tool itself is read-only with no side effects, making it a Read category risk.

From the tool's definition Tool name 'query_account_asset' and description '查询账户资产' (query account assets) indicate data retrieval without modification.

Documented attack patterns abuse exactly the kind of access query_account_asset gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and QMT-MCP-Server, and nothing reaches the server without passing your rules. This is the rule we recommend for query_account_asset:

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

query_account_asset is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register QMT-MCP-Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the query_account_asset tool do? +

查询账户资产. It is categorised as a Read tool in the QMT-MCP-Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_account_asset? +

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

What risk level is query_account_asset? +

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

Can I rate-limit query_account_asset? +

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

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

query_account_asset is provided by the QMT-MCP-Server MCP server (nnquant/qmt-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every QMT-MCP-Server tool call.

Deterministic rules across all 4 QMT-MCP-Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4 QMT-MCP-Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.