skillet_install · Skillet MCP: Risk & Policy

WHAT IT DOES

What skillet_install does on Skillet

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

WHY IT NEEDS A POLICY

Why skillet_install needs a policy

This tool creates new files and modifies the project structure by installing skills. While not destructive (files can theoretically be removed), it is Write-category because it modifies the local project state. Severity is medium because installing untrusted or malicious skills could compromise the project, but the blast radius is limited to the local project scope and the registry is presumably curated.

From the tool's definition Tool name 'skillet_install' performs installation action, description states 'Install a skill from the registry into this project (.claude/skills/)', which creates or modifies project files irreversibly by adding new skill files to the project directory.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

skillet_install Rate-limited

skillet_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": {
    "skillet_install": {
      "limits": [
        {
          "counter": "skillet_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 Skillet, so you can run agents against it safely.

FAQ

Questions about skillet_install

What does the skillet_install tool do? +

Install a skill from the registry into this project (.claude/skills/). Pass the registry. It is categorised as a Write tool in the Skillet MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on skillet_install? +

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

What risk level is skillet_install? +

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

Can I rate-limit skillet_install? +

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

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

skillet_install is provided by the Skillet MCP server (jnmetacode/skillet). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.