Compare portfolios across multiple authenticated brokers in your session
AI agents call compare_portfolios 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.
Comparing portfolios is a read-only operation that retrieves and presents portfolio information from multiple brokers for analysis. It has no side effects, does not modify data, execute commands, delete anything, or move funds. The operation is constrained to viewing already-authenticated broker sessions. Low severity because misuse would only expose existing portfolio data the user already has access to.
From the tool's definition Tool name is 'compare_portfolios' and description states it 'Compare portfolios across multiple authenticated brokers in your session' — this is a query/retrieval operation that reads portfolio data without modification.
Documented attack patterns abuse exactly the kind of access compare_portfolios 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 compare_portfolios:
{
"version": "1",
"default": "deny",
"tools": {
"compare_portfolios": {}
}
}compare_portfolios 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.
Compare portfolios across multiple authenticated brokers 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 compare_portfolios: 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.
compare_portfolios 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 compare_portfolios 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 compare_portfolios. 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.
compare_portfolios 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.