Get current stock balance information from Korea Investment & Securities
AI agents call inquery-balance to retrieve information from KIS REST API 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 balance information from the KIS API without creating, modifying, or deleting data. While classified as Read, severity is elevated to 'medium' rather than 'low' because balance information reveals sensitive financial account details that could inform adversarial decision-making if an AI agent queries balances to strategically plan subsequent financial operations (e.g., transfer limits,…
From the tool's definition Tool name 'inquery-balance' and description 'Get current stock balance information' indicate a data retrieval operation with no modification or side effects. The verb 'Get' and 'inquery' (query) are characteristic of Read operations.
Documented attack patterns abuse exactly the kind of access inquery-balance gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and KIS REST API MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for inquery-balance:
{
"version": "1",
"default": "deny",
"tools": {
"inquery-balance": {}
}
}inquery-balance 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 stock balance information from Korea Investment & Securities. It is categorised as a Read tool in the KIS REST API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the KIS REST API MCP Server MCP server in PolicyLayer and add a rule for inquery-balance: 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 KIS REST API MCP Server. Nothing to install.
inquery-balance 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 inquery-balance 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 inquery-balance. 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.
inquery-balance is provided by the KIS REST API MCP Server MCP server (migusdn/kis_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from KIS REST API MCP Server, 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.
15 KIS REST API MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.