install_packages · Cachyos MCP: Risk & Policy

WHAT IT DOES

What install_packages does on Cachyos

AI agents invoke install_packages to trigger actions in Cachyos. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why install_packages needs a policy

Installing packages executes privileged system operations that modify system state by adding software. While it is reversible (packages can be uninstalled), the act of installing packages can introduce new executables, services, and system-level changes with significant security implications. This falls under Execute as it triggers external operations with effects that depend on the arguments provided.

From the tool's definition [ACTION] Install one or more repo packages (space-separated)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

install_packages Rate-limited

install_packages stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_packages": {
      "limits": [
        {
          "counter": "install_packages_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about install_packages

What does the install_packages tool do? +

[ACTION] Install one or more repo packages (space-separated). It is categorised as a Execute tool in the Cachyos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on install_packages? +

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

What risk level is install_packages? +

install_packages is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit install_packages? +

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

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

install_packages is provided by the Cachyos MCP server (raindancer118/cachyos-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.