kage_setup_agent

THE RISK

Medium Risk

Why kage_setup_agent needs a policy

The tool creates or generates configuration/setup instructions for integrating MCP servers with different coding agents and IDEs. This is a write operation that produces new setup data or files, but the impact is reversible and non-destructive (setup instructions can be discarded or reconfigured). It does not execute code, delete data, or move money.

From the tool's definition Tool name includes 'setup' and description states it 'Generate[s] MCP/setup instructions' for various AI coding agents and environments.

Documented attack patterns abuse exactly the kind of access kage_setup_agent gives an agent:

POLICY

How to control kage_setup_agent

PolicyLayer is an MCP gateway — it sits between your AI agents and Kage, and nothing reaches the server without passing your rules. This is the rule we recommend for kage_setup_agent:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "kage_setup_agent": {
      "limits": [
        {
          "counter": "kage_setup_agent_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

kage_setup_agent stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Kage — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Kage tools

Destructive kage_context_slot_delete Delete a repo-local context slot by label. Destructive kage_compact Consolidate repo memory: prune dead citations, deprecate hard-stale packets, and surface n Execute kage_refresh Rebuild repo indexes, code graph, memory graph, metrics, and stale-memory metadata. Agents Write kage_graph_registry Build a signed graph-registry manifest for generated memory graph, code graph, indexes, me Write kage_structural_index Build the complete cache-backed structural index for large repos. This covers all supporte Write kage_observe Store an automatic local observation event from an agent session. Observations are privacy Write kage_capture Create a repo-local Kage memory packet immediately. Org/global promotion still requires ex Write kage_code_index Write external code index artifacts consumed by the code graph. Prefers SCIP when scip-typ

All 62 Kage tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about kage_setup_agent

What does the kage_setup_agent tool do? +

Generate MCP/setup instructions for Codex, Claude Code, Cursor, Windsurf, Gemini CLI, OpenCode, Cline, Goose, Roo Code, Kilo Code, Claude Desktop, Aider, or generic MCP. It is categorised as a Write tool in the Kage MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on kage_setup_agent? +

Register the Kage MCP server in PolicyLayer and add a rule for kage_setup_agent: 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 Kage. Nothing to install.

What risk level is kage_setup_agent? +

kage_setup_agent is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit kage_setup_agent? +

Yes. Add a rate_limit block to the kage_setup_agent 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 kage_setup_agent completely? +

Set action: deny in the PolicyLayer policy for kage_setup_agent. 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 kage_setup_agent? +

kage_setup_agent is provided by the Kage MCP server (@kage-core/kage-graph-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Kage tool call.

Start from Kage, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →