Purpose: Per-symbol paper position deep-dive (position + recent trades + decisions). When to call: full context for one ticker. Prerequisites: confirm the symbol holds a position via get_positions. Next steps: get_signal_detail, get_role_analysis. Caveats: returns an error envelope when no positi...
Part of the OneQAZ Trading Intelligence server.
Free to start. No card required.
AI agents call get_position_detail to retrieve information from OneQAZ Trading Intelligence 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 get_position_detail 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.
{
"version": "1",
"default": "deny",
"tools": {
"get_position_detail": {}
}
}See the full OneQAZ Trading Intelligence policy for all 32 tools.
These attack patterns abuse exactly the kind of access get_position_detail gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Purpose: Per-symbol paper position deep-dive (position + recent trades + decisions). When to call: full context for one ticker. Prerequisites: confirm the symbol holds a position via get_positions. Next steps: get_signal_detail, get_role_analysis. Caveats: returns an error envelope when no position exists for the symbol. Args: market_id: Market ID (crypto, kr_stock, us_stock; aliases coin/kr/us accepted) coin: Symbol (e.g., BTC, ETH, AAPL) Disclaimer: Information only, not investment advice.. It is categorised as a Read tool in the OneQAZ Trading Intelligence MCP Server, which means it retrieves data without modifying state.
Register the OneQAZ Trading Intelligence MCP server in PolicyLayer and add a rule for get_position_detail: 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 OneQAZ Trading Intelligence. Nothing to install.
get_position_detail 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_position_detail 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_position_detail. 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_position_detail is provided by the OneQAZ Trading Intelligence MCP server (pypi:oneqaz-trading-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 32 OneQAZ Trading Intelligence 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.