Get daily position counts for a strategy across all symbols. Returns time-series data showing how many positions were open each trading day - perfect for graphing capital deployment over time. Requires trade-level data (available for runs after Dec 2025).
AI agents call get_daily_position_counts to retrieve information from Mcp Strategy Research Db without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query of historical trade data to retrieve position count metrics for analysis and graphing. It has no side effects, cannot modify the database, execute code, or create financial obligations. The worst-case misuse scenario (returning incorrect analytical data) has minimal blast radius compared to tools that could modify strategy records or execute arbitrary queries.
From the tool's definition Tool retrieves and returns time-series data showing daily position counts without modifying data. Described as 'Get daily position counts' and 'Returns time-series data'. No mutation, deletion, execution, or financial transaction capability indicated.
Attacks that exploit this kind of access
Get daily position counts for a strategy across all symbols. Returns time-series data showing how many positions were open each trading day - perfect for graphing capital deployment over time. Requires trade-level data (available for runs after Dec 2025). It is categorised as a Read tool in the Mcp Strategy Research Db MCP Server, which means it retrieves data without modifying state.
Register the Mcp Strategy Research Db MCP server in PolicyLayer and add a rule for get_daily_position_counts: 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 Mcp Strategy Research Db. Nothing to install.
get_daily_position_counts 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_daily_position_counts 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_daily_position_counts. 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_daily_position_counts is provided by the Mcp Strategy Research Db MCP server (locupleto/mcp-strategy-research-db). 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 →