install · Kit MCP: Risk & Policy

WHAT IT DOES

What install does on Kit

AI agents use install to create or update resources in Kit — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kit environment.

WHY IT NEEDS A POLICY

Why install needs a policy

This tool creates/registers a new server entry in an IDE (reversible configuration change), which is a Write operation. Severity is medium because misconfiguration could affect IDE behavior or expose unintended server access, but the action itself is not destructive, financial, or arbitrary code execution.

From the tool's definition Tool name 'install' with description 'Register this kit-mcp server into an IDE' indicates a modification operation that adds or registers a server into an IDE configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

install Rate-limited

install 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.

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Kit, so you can run agents against it safely.

FAQ

Questions about install

What does the install tool do? +

Register this kit-mcp server into an IDE\. It is categorised as a Write tool in the Kit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on install? +

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

What risk level is install? +

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

Can I rate-limit install? +

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

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

install is provided by the Kit MCP server (luanpdd/kit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.