Critical Risk →

call-kis-api

Call any collected KIS REST API by group/api_type using cataloged interface metadata

How to control call-kis-api ↓

What call-kis-api does on KIS REST API MCP Server

AI agents use call-kis-api to commit financial operations through KIS REST API MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.

Critical Risk

Why call-kis-api needs a policy

This tool can invoke any KIS REST API endpoint, which per the server description includes stock trading operations (buy/sell orders), account management, and financial transactions. Because it can trigger arbitrary API calls including trading operations, it spans Financial (most severe) category.

From the tool's definition Call any collected KIS REST API by group/api_type using cataloged interface metadata — combined with server description: 'enabling domestic and foreign stock trading, price checks, and account management'

Documented attack patterns abuse exactly the kind of access call-kis-api gives an agent:

How to control call-kis-api

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 call-kis-api:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "call-kis-api": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

Any call to call-kis-api is blocked until a human approves it. The rest of the server keeps working.

  1. Create a free account and register KIS REST API MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
GATE THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about call-kis-api

What does the call-kis-api tool do? +

Call any collected KIS REST API by group/api_type using cataloged interface metadata. It is categorised as a Financial tool in the KIS REST API MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on call-kis-api? +

Register the KIS REST API MCP Server MCP server in PolicyLayer and add a rule for call-kis-api: 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.

What risk level is call-kis-api? +

call-kis-api is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit call-kis-api? +

Yes. Add a rate_limit block to the call-kis-api 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.

How do I block call-kis-api completely? +

Set action: deny in the PolicyLayer policy for call-kis-api. 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.

What MCP server provides call-kis-api? +

call-kis-api 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.

Enforce policy on every KIS REST API MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.