Group executed orders by tag and infer strategy-level P&L from positions matched by ref_id.
AI agents call get_strategy_pnl to retrieve information from Nubra MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs analytics and reporting on historical trade data—it queries executed orders and positions to calculate and display profit/loss metrics. There is no creation, modification, deletion, or execution of external operations. The read-only nature of querying existing trading positions and calculating derived metrics (P&L) places this squarely in the Read category.
From the tool's definition The tool 'get_strategy_pnl' retrieves and groups executed orders by tag, inferring strategy-level P&L from matched positions.
Attacks that exploit this kind of access
Group executed orders by tag and infer strategy-level P&L from positions matched by ref_id. It is categorised as a Read tool in the Nubra MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Nubra MCP Server MCP server in PolicyLayer and add a rule for get_strategy_pnl: 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 Nubra MCP Server. Nothing to install.
get_strategy_pnl 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_strategy_pnl 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_strategy_pnl. 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_strategy_pnl is provided by the Nubra MCP Server MCP server (socials-zanskar/nubra-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →