AI agents call get_instrument_detail_tool 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.
This tool retrieves instrument/stock details from the QMT platform without side effects. The naming convention ('get_') and positioning among sibling tools (download, get_market_data, get_current_time) suggest it is a read-only query tool. While the description is empty, the tool name and context strongly indicate data retrieval functionality with no capability to modify or delete data.
From the tool's definition Tool name 'get_instrument_detail_tool' indicates a query/retrieval operation. Server description states it enables users to 'query stock details' and 'analyze stock performance.' The tool appears designed to fetch stock information rather than modify,…
Documented attack patterns abuse exactly the kind of access get_instrument_detail_tool 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 get_instrument_detail_tool:
{
"version": "1",
"default": "deny",
"tools": {
"get_instrument_detail_tool": {}
}
}get_instrument_detail_tool 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_instrument_detail_tool. It is categorised as a Read tool in the QMT MCP Server MCP Server, which means it retrieves data without modifying state.
Register the QMT MCP Server MCP server in PolicyLayer and add a rule for get_instrument_detail_tool: 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.
get_instrument_detail_tool 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 get_instrument_detail_tool 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 get_instrument_detail_tool. 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.
get_instrument_detail_tool is provided by the QMT MCP Server MCP server (jm12138/qmt-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from QMT 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.
5 QMT MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.