AI agents call read_account to retrieve information from QuantConnect without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves account information without modifying or executing operations. However, account status data may include sensitive financial or operational details (balance, subscription tier, usage limits), which justifies 'medium' severity rather than 'low' — an agent with access could exfiltrate account metadata, though no direct financial transactions or destructive actions are possible.
From the tool's definition Tool name is 'read_account' and description states 'Read the organization account status' — the verb 'read' and explicit 'Read' indicate data retrieval with no modification.
Documented attack patterns abuse exactly the kind of access read_account gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and QuantConnect, and nothing reaches the server without passing your rules. This is the rule we recommend for read_account:
{
"version": "1",
"default": "deny",
"tools": {
"read_account": {}
}
}read_account 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.
Read the organization account status. It is categorised as a Read tool in the QuantConnect MCP Server, which means it retrieves data without modifying state.
Register the QuantConnect MCP server in PolicyLayer and add a rule for read_account: 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 QuantConnect. Nothing to install.
read_account 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 read_account 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 read_account. 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.
read_account is provided by the QuantConnect MCP server (quantconnect/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 64 QuantConnect tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
64 QuantConnect tools catalogued and risk-classified — across an index of 42,500+ MCP servers.