Build a Vol_Regime x Trend_Direction matrix (18 cells) across all profiled strategies. Shows per-strategy stats in each cell, detects overlap (2+ strategies in same cell), blind spots (cells with zero trades), and thin-data warnings. Optionally filter to a single block or aggregate across all blo...
AI agents invoke portfolio_structure_map to trigger actions in Tradeblocks. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
portfolio_structure_map triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
Build a Vol_Regime x Trend_Direction matrix (18 cells) across all profiled strategies. Shows per-strategy stats in each cell, detects overlap (2+ strategies in same cell), blind spots (cells with zero trades), and thin-data warnings. Optionally filter to a single block or aggregate across all blocks. It is categorised as a Execute tool in the Tradeblocks MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Tradeblocks MCP server in PolicyLayer and add a rule for portfolio_structure_map: 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 Tradeblocks. Nothing to install.
portfolio_structure_map is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the portfolio_structure_map 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 portfolio_structure_map. 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.
portfolio_structure_map is provided by the Tradeblocks MCP server (tradeblocks-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.