gvm_governance

Enforce policy-driven governance for outbound API calls with WAL logging.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/skwuwu/analemma-gvm-openclaw --skill gvm-governance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gvm_governance
Source: https://github.com/skwuwu/analemma-gvm-openclaw/tree/main/skills/gvm-governance
Command: npx skills add https://github.com/skwuwu/analemma-gvm-openclaw --skill gvm-governance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI agents require governance over external API calls, audit trails, and integrity checks. This Skill provides a governance kernel to enforce policies, log decisions, detect forgery, and manage checkpoint rollback for AI I/O.

Core Features & Use Cases

  • Enforce policy-driven governance for outbound API calls via gvm_fetch/gvm_read/gvm_write with automatic credential injection and a write-ahead log (WAL).
  • Maintain immutable audit logs for forensic analysis, compliance, and cost tracking.
  • Detect and prevent forgery by cross-checking declared operations against actual requests, with rollback support on Deny.
  • Run and monitor governance state across ABAC/SRR layers, providing safe execution of agent workflows.

Quick Start

Install the GVM proxy, configure it, and run your agent through the gateway to start enforcing governance and auditing API calls.

Frequently Asked Questions about gvm_governance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce policy-driven governance for outbound API calls made by AI agents?

You can enforce policy-driven governance for outbound API calls by running agent workflows through a proxy gateway that applies ABAC/SRR policies, automatically injects credentials, and validates declared operations against actual requests before execution.

What is the best way to maintain immutable audit logs for AI agent API interactions?

Maintaining immutable audit logs for AI agent API interactions requires a write-ahead log (WAL) that records every governance decision and external request, ensuring data integrity for forensic analysis, compliance, and cost tracking.

How does write-ahead logging work for AI agent API governance and rollback?

Write-ahead logging for AI agent API governance records intended operations before execution, enabling the system to cross-check declared actions against actual requests, detect forgery, and trigger automatic rollback when a policy Deny decision is enforced.

Do I need specific policy layers to prevent API call forgery in automated agent workflows?

Yes, preventing API call forgery in automated agent workflows requires ABAC/SRR policy enforcement layers to cross-check declared operations against actual requests, ensuring safe execution and providing rollback support on Deny across multiple servers and integrations.

Can I monitor governance state across multiple servers and integrations for AI I/O?

You can monitor governance state across multiple servers and integrations by running the governance kernel, which provides real-time decisioning and auditing across all automated agent workflows and external API interactions.

What tools are required to set up a governance proxy for AI agent API access?

Setting up a governance proxy for AI agent API access requires the gvm_fetch, gvm_read, and gvm_write toolset to operate, enforcing policies, logging decisions, detecting forgery, and managing checkpoint rollback for AI I/O.