Skip to content

Guardana Control 0.5.0-alpha

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 02 Oct 14:21
· 303 commits to main since this release
Immutable release. Only release title and notes can be modified.

An author can now see why a call got its decision: policy explain names the
rules that matched and the fields a rule could not read. Two starter policy
packs, read-only and approval-for-writes, come with cases that show what they
decide. A guide puts the plane between an MCP client and a server already in
use. An audit before the release fixed defects, among them: a call the agent
cancelled could lose its closing record, and enough of them blocked every later
call; other accounts could write the evidence directory; a configuration
refusal printed a header credential; and some MCP clients refused the plane's
answers as schema errors. docs/status.md says what is
implemented and what is experimental. Nothing here is a security boundary
yet.

Added

  • guardana-control policy explain <case> decides one case as policy test
    does and says how: the decision's verdict, action, mode, policy digest and
    codes, what the kernel found before the policy, and a line per rule, matched,
    undetermined with the field it could not read and the input that field
    lacked, or not matched on the fields that failed. It reads the kernel's own
    evaluation, so it never describes a decision the kernel would not make for
    the same case
    (ADR-0036,
    reference/policy-explain.md).
  • Two starter policy packs under examples/starter-packs/, read-only and
    approval-for-writes, each a document with allow, deny and unknown cases, and
    a page that says what each assumes about the plane and leaves unguarded
    (reference/starter-packs.md).
  • A guide that puts the plane between an MCP client and a server already in
    use, and a profile for the MCP project's reference filesystem server that
    classifies its 14 tools and holds every write for approval
    (guides/connect-an-existing-mcp-setup.md).

Fixed

  • A tools/call the plane blocked or held for a tool that declares an output
    schema reached the agent as a schema error from any client that checks
    structured content, the MCP project's own TypeScript client among them,
    instead of APPROVAL_PENDING or the block's codes. The plane's own answers
    now carry their fields in the result's _meta under its namespace and no
    structured content.
  • A configuration value the reader refused (a flow character, an unknown
    escape, an unclosed quote) was printed in doctor's and run's refusal,
    credentials included: an export.headers or pdp.headers value, the
    pdp.proxy, an endpoint with userinfo. Those are now named without the
    value.
  • The evidence spool took a directory other accounts could write, or another
    account owned, and appended through a link put at a segment's name. It now
    refuses both, as the approvals, runs and pause directories do, and opens
    every segment without following a link.
  • The configuration reader kept a tag (!!str x) or a single-quoted value
    ('acme') as text, marks included, so a tenant id written 'acme' matched
    no run and no rule. Both are now refused; quote a value with double quotes.
  • A call the agent cancelled after the plane handed it out lost its closing
    record: the trail stopped at ACTION_STARTED, material calls halted, and the
    spool kept the call's reservation, so enough cancelled calls blocked every
    call until a restart. The closing record is now written whatever the agent
    does.
  • A stateful HTTP session was never ended, so sessions a client opened and
    abandoned held the plane's memory until it stopped. A session idle for 30
    minutes now ends.
  • A shorten_timeout obligation whose ms a duration cannot hold wrapped
    when converted, and the call ran with no bound or with one nobody wrote. It
    is now refused like a non-positive ms.

Image: ghcr.io/guardana/control-gateway@sha256:a6ed11ae7ca4aab05164142c5a368a3d7269e78810cdf82b54ed0d20cee5a439