Get account information
AI agents call get_account_info to retrieve information from Shioaji MCP Server 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, deleting, or executing any operations. It is a read-only query operation. Severity is medium rather than low because account information (balance, positions, account status) is sensitive financial data whose exposure could enable social engineering or unauthorized trading decisions, though the tool itself does not move money or execute trades.
From the tool's definition Tool name 'get_account_info' and description 'Get account information' indicate retrieval of data with no side effects. The broader server context involves 'market data retrieval and order management', and this tool performs only data retrieval.
Attacks that exploit this kind of access
Get account information. It is categorised as a Read tool in the Shioaji MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Shioaji MCP Server MCP server in PolicyLayer and add a rule for get_account_info: 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 Shioaji MCP Server. Nothing to install.
get_account_info 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_account_info 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_account_info. 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_account_info is provided by the Shioaji MCP Server MCP server (offbeat-studio/shioaji-mcp). 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 →