AI Knowledge Hub
Menu

Tools Mcp / Agentops

Agent Control Plane MCP Server

Launchable local MCP authority for tenant-scoped policy decisions, exact human approvals, signed execution grants, ordered action records, restart recovery, and tamper-evident audit verification.

Access

Read and write · Local agent control plane

Setup requiredLocal programRequirements & limits

Inputs

The released example shows these fields. Check the guide for which are required.

  • tool
  • arguments

Outputs

The released example shows these fields. Check the guide for which are required.

  • schema_version
  • decision_id
  • tenant_id
  • actor_id
  • effect
  • matched_rule_ids
  • approver_roles
  • approval_ttl_seconds
  • reason_code
  • policy_id
  • policy_version
  • policy_digest
  • decided_at

Before you begin

  • Node.js 22 or newer.
  • CONTROL_PLANE_STORE, signed identity, identity public key, audit key, and role-specific grant keys: issuer key pair for agents or public key only for executors.
  • A separately scoped administrator identity to install policy and record human approval decisions.

Try this first

Review the setup requirements, access boundaries and release guide before connected use.

Limits for this step
  • This server does not execute provider mutations; governed executors must verify grants at their own effect boundary.
  • The deterministic local store assumes one filesystem host and does not provide multi-host consensus.
  • Key rotation requires an explicit operator migration; silent fallback to an old or unknown key is not supported.
  • The MCP runtime can request approval but cannot install policy or decide approvals; administrator authority is available only through the separate operator entrypoint.
Review setup requirements

Summary sources · Catalogue metadata, tool.yaml, TOOL.md, examples/input.json, examples/output.json · v0.2.1 · Release package

View capabilities and accessHide capabilities and accessv0.2.1

What it can do

  • Authenticate separate proposing-agent and executor identities and enforce tenant, capability, and provider-account scope.
  • Evaluate versioned policy outside the model and fail closed for unmatched actions.
  • Create exact approval requests and revalidate separately recorded human decisions.
  • Issue short-lived signed execution grants for downstream governed executors.
  • Revalidate current policy, approval, and executor scope while atomically claiming a grant at the external effect boundary.
  • Recover an exact durable claim for historical reconciliation, then separately revalidate current authority before any not-yet-started provider effect.
  • Persist authenticated state, hashed receipt references, compacted recovery intents, idempotent action evidence, and a signed hash-chained audit log.

Access limits

The MCP runtime can request approval but cannot install policy or decide approvals; administrator authority is available only through the separate operator entrypoint.

Trust boundary · local-tool

Credentials and setup

  • Runtime-owned signed identity and independent signing keys
  • Absolute private control-plane store path

Install tool files

These commands install package files and generate runtime configuration where supported. Confirm discovery in your agent app, then check configuration, authentication and a first useful operation.

Install (Codex)

./bin/skills-hub install --module tools --entry agentops/[email protected] --runtime codex

Install (Claude)

./bin/skills-hub install --module tools --entry agentops/[email protected] --runtime claude

Install (Generic)

./bin/skills-hub install --module tools --entry agentops/[email protected] --runtime generic --target ./my-agent/tools-mcp

How You Can Use This

Setup required

Resource form: Local program

Configuration, credentials or runtime bindings are required. Check the prerequisites and limits for your intended environment.

First run: Create signed runtime and administrator identities, install a tenant policy with the operator CLI, then register .mcp.json.

Setup required

  • Node.js 22 or newer.
  • CONTROL_PLANE_STORE, signed identity, identity public key, audit key, and role-specific grant keys: issuer key pair for agents or public key only for executors.
  • A separately scoped administrator identity to install policy and record human approval decisions.

Current limits

  • This server does not execute provider mutations; governed executors must verify grants at their own effect boundary.
  • The deterministic local store assumes one filesystem host and does not provide multi-host consensus.
  • Key rotation requires an explicit operator migration; silent fallback to an old or unknown key is not supported.
What installation and verification mean
File installation
Places package files and generated configuration in the selected directories.
Native discovery
Your agent app finds and accepts the instructions, tools or plugin registrations.
Mock execution
Exercises sample fixtures. Connected data and provider effects need a separate check.
Connected operation
Requires current configuration, provider authentication, scoped permissions and a successful operation in your intended environment.

Declared compatibility

Maintainer-reviewed information for version 0.2.1 · Reviewed 2026-10-31. This is not a live provider check.

  • Runtime: Node.js 22 or newer
  • Local MCP control plane using Node built-ins; no external provider API or SDK dependency.

Limits

  • Requires configured identities, keys, policies and a private local filesystem store.
  • Coordinates authority and records on one filesystem host; it does not execute provider mutations or provide multi-host consensus.

Reviewed control plane release implementation

Classification: declared

Technical details and release files

Review and lifecycle

Review maturity: Experimental

Security review declaration: Not declared

Lifecycle: Active

These release declarations are separate from evidence that a workflow operates in your environment.

Runtime & Dependencies

ID: agentops/agent-control-plane-server

Tags: mcp, governance, policy, audit, approvals

Runtimes: codex, claude, generic

Dependencies & Setup

MCP servers: Not documented

APIs: Not documented

Local tools: Not documented