Get current trading positions from active or specific broker in your session
AI agents call get_positions to retrieve information from Turtlestack Lite without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries current trading position data from a broker. It has no side effects, does not modify data, execute code, or trigger external state changes. Even in a trading context, querying positions is fundamentally a read operation. The blast radius of misuse is minimal—an agent could only view financial positions, not alter them or commit financial obligations.
From the tool's definition Tool name 'get_positions' and description 'Get current trading positions from active or specific broker' indicate data retrieval with no modification or execution.
Documented attack patterns abuse exactly the kind of access get_positions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Turtlestack Lite, and nothing reaches the server without passing your rules. This is the rule we recommend for get_positions:
{
"version": "1",
"default": "deny",
"tools": {
"get_positions": {}
}
}get_positions 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 current trading positions from active or specific broker in your session. It is categorised as a Read tool in the Turtlestack Lite MCP Server, which means it retrieves data without modifying state.
Register the Turtlestack Lite MCP server in PolicyLayer and add a rule for get_positions: 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 Turtlestack Lite. Nothing to install.
get_positions 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_positions 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_positions. 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_positions is provided by the Turtlestack Lite MCP server (turtlehq-tech/turtlestack-lite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Turtlestack Lite, 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.
45 Turtlestack Lite tools catalogued and risk-classified — across an index of 43,000+ MCP servers.