Skip to content

Muppy MCP permissions

Being deployed

These rules are being deployed. Muppy does not follow all of them yet. Until it does, The rules of engagement describes what your version does today.

This page holds the rule that decides whether an AI agent acts alone on a Muppy record through the MCP, or needs a human's permission.

The rule

Outside Production, AI Managed lets the agent act alone. Production opens only with a human permission.

  1. Reading is free, and so is calling an information method or a safe method. Acting goes through the record's gate: writing, creating, deleting, calling any other method.
  2. A record is Production or outside Production. Its Muppy qualifier says which: its own, or the one of the record that a related field of its model points to. A record with neither is Production.
  3. In Production, the agent never acts without a permission: the approval of that call, or a running Grant for Duration.
  4. Outside Production, the agent acts alone when the record is AI Managed, or when a Grant for Duration is running. Otherwise it needs the approval of the call.
  5. A decommissioned record (decom) refuses every action, reading included.
AI Managed off AI Managed on
Outside Production permission alone
Production permission permission
decom refused refused

Permission means the approval of that call, or a Grant for Duration running on the record. A Grant opens the record, Production included, until it ends.

Terms

Term Meaning
Muppy qualifier A qualifier record: Production, Staging, Development… What counts is its effective base category.
MCP qualifier What the MCP engine reads on a record to decide a call. The gate derives it from the Muppy qualifier, the AI Managed switch and the running Grant.
Gate What decides for a record: its Muppy qualifier, its AI Managed switch and its running Grant.
AI Managed The switch that lets agents act alone on a record outside Production. Only a human sets it.
Grant for Duration Opens a record to agents for 15 minutes, 1 hour, 4 hours or until a date. Only a human grants it.
Permission The approval of one call, or a running Grant for Duration.
Information method A method that returns what Muppy already knows, and changes nothing.
Safe method A method that rereads a real object (a host, a DNS zone, a provider account) and updates Muppy's copy of it, without changing anything on the machine or at the provider. Syncing a domain with its zone, Update Facts and collecting metrics are safe. A method that updates what a later gesture sends to a machine is not safe, even if it sends nothing itself.

How an agent asks for the approval of a call, and how you answer it, is on Muppy MCP — What an Agent Can Do.

Production or not

Category of the Muppy qualifier For the gate
dev, test outside Production
demo, staging, infra, prod Production
tmpl Production. It is the qualifier of App Definitions, and every new App Server is a copy of one.
no Muppy qualifier, and no related field Production
decom no action

Where a record's qualifier comes from

Nothing is guessed. Each model exposed to the MCP declares where its Muppy qualifier comes from, in one of two ways, and no other:

  • Its own qualifier: hosts and App Servers.
  • A related field to the record that gives it. The field follows what the record serves, not where it runs:
    • a systemd unit follows the App Server whose application it serves, not its host;
    • a Traefik Server follows its host;
    • a Traefik application follows its App Server, not the Traefik Server that publishes it. An application without an App Server is Production.

A qualifier is never aggregated from what a gesture reaches:

  • A CIDR Dynamic Range has no qualifier. It is Production, and a Grant opens it.
  • Sending a configuration to a Traefik Server is judged on the record you call, not on everything the Traefik Server publishes.

The gate a record follows

A record has its own gate, with its AI Managed switch and its Grant: hosts, App Servers, Traefik Servers, OVH accounts, CIDR Dynamic Ranges. Otherwise it follows the gate of the record its related field points to.

Only a human opens a gate. Through the MCP, the fields of the gate are read-only: an agent cannot set AI Managed or a Grant on any record.

Free methods

Each model names its information methods and its safe methods. Every other method goes through the gate.

Reading a file is not an information method: a file can hold a secret, such as /etc/muppy.env.

One record per call

A write or a delete on several records fails, whatever their gates. Call once per record.

Each record is an arbitration of its own, and a permission request carries one.