Skip to content

PRÆTORE v0.3.5

Choose a tag to compare

@github-actions github-actions released this 15 Nov 23:17
· 223 commits to main since this release
b6d668a

praetore-mcp: init writes a default-deny policy (no
allow-all-mcp-tool-calls), policy coverage reports what the policy
decides for each tool a server lists, and dashboard serves a read-only
local page over the receipts journal. Also carries everything merged to
main since v0.3.4, including the dashboard minors and latency tests that
tolerate a loaded machine from #175.

Changed

  • praetore-mcp: init writes a default-deny policy (behavior change for
    enforce mode).
    The policy has no rules. Before, it had
    allow-all-mcp-tool-calls, which allowed every tools/call that no other
    rule matched, so DENY rules that named tools left every other tool
    allowed: with DENY rules per tool, copy_file and append_file of
    @modelcontextprotocol/server-filesystem@2.3.0 were allowed because no
    rule named them. Now, in enforce mode, every tools/call that no rule
    allows is denied; allow tools with
    praetore-mcp policy allow --id ID --server NAME --tool NAME. No rule is
    needed to start a server: only tools/call is evaluated, so
    initialize, tools/list and the rest of the MCP traffic pass. Observe
    mode is unchanged and never blocks. Existing homes keep their policy:
    init on a home that has an allow-all rule leaves it in place and prints
    a warning with praetore-mcp policy remove --id allow-all-mcp-tool-calls.
    Not in v0.3.4: init in that release still writes
    allow-all-mcp-tool-calls (#167). The GUIDE records that fact and how
    to remove the rule from a home created by that release (#168).
  • praetore-mcp: policy check warns about allow-all next to tool
    rules.
    When the policy has an allow-all rule and DENY or
    REQUIRE_APPROVAL rules for specific tools, it says that tools those rules
    do not name are allowed and suggests policy coverage. policy deny,
    require-approval and allow print the same warning after the change
    (#167).

Added

  • praetore-mcp dashboard [--dir DIR] [--port N] [--expected-head HEX].
    A read-only local page over receipts/*.jsonl, served on 127.0.0.1 only
    (default port 8787, 0 picks a free one). Any other address is refused.
    The page shows a summary (total, ALLOW, DENY, active policy id, version
    and digest, and a warning when an allow-all rule meets enforce receipts),
    the decisions table (local time and UTC, server, tool, arguments,
    decision, rule or default deny, mode, evidence id) with filters, and
    each receipt's full JSON, path_check and agent, attester and authority
    signatures with their key ids. The verification status, per receipt and
    for the journal, with seq/prev and the journal head, comes from the code
    behind praetore-mcp verify. To share it, verify's per-receipt check
    is split into one result per check (receipts::check_evidence). verify
    prints the same output as before. HTML, CSS and JS are embedded in the
    binary. Nothing is loaded from the network or written under DIR. Only
    GET requests with a loopback Host are answered. Texts in Spanish,
    English and Portuguese. The table shows 100 receipts per page, newest
    first; the filters (decision, tool, time range, text) run on the server
    over the whole journal. The verification result is kept in memory until
    a file verify reads changes, so a reload of an unchanged 10,000-receipt
    journal does not run verify again (#166).
  • praetore-mcp dashboard: home, live, chain and information views. The
    page opens on a home view with the agent, the servers, the mode, the
    verification result and the ALLOW, DENY and pending counts. The live view
    draws the newest receipts: an allowed call reaches its box, a denied one
    stops at a red bar that shows the rule id, default deny or the engine
    check, and a call waiting for approval stops at an amber bar marked as an
    unsigned notice that verify does not check. The chain view draws the
    receipts in seq order joined by the prev hash link and shows the link
    cut, with the reason, where verify fails. Opening a receipt shows its
    tool, arguments, rule, mode, local time and UTC, evidence id, seq, prev
    and its verify result. The live view marks a receipt that verify
    rejects, with the reason, and moves only when a receipt arrives, the
    verify result changes or the pending calls change. Live and chain each
    have a text list view with the same content, and nothing moves when the
    system asks for reduced motion. The drawings use a 2D canvas and code
    embedded in the binary; the page keeps the same Content-Security-Policy
    and loads nothing from the network. The page now uses one dark color
    scheme (#172, #173).
  • praetore-mcp: policy coverage [--dir DIR] [--server NAME] -- <command> [args...]. Starts the MCP server, sends initialize and tools/list
    (every page), closes it, and prints for each tool what the policy
    decides: the rule that applies or default deny, and whether a rule
    depends on an argument. Tools allowed only by an allow-all rule are
    listed apart. Exit code 0 when there are none, 1 when there is one, 2 on a
    usage error or when the server cannot be started or does not answer. It
    sends no tools/call and writes nothing under DIR. For each tool
    denied because no rule names it, it prints the
    praetore-mcp policy allow --id ... --server ... --tool ... line that
    allows it, quoted to run as printed in a POSIX shell. Tools with a rule
    that depends on an argument get no line, and neither do tool names with
    characters outside A-Z a-z 0-9 _ - . (#167, #170).
  • Commands that praetore-mcp prints with --dir DIR quote DIR when it
    has spaces or other characters a shell would interpret.
  • scripts/mcp-smoke.py checks policy coverage against
    @modelcontextprotocol/server-filesystem@2.3.0, and the smoke test now
    allows read_text_file with an explicit rule.

Fixed

  • praetore-mcp dashboard: the live view writes the whole reason verify
    gives for a rejected receipt, over up to three lines, and says when a
    longer one continues in the receipt detail. It was clipped (#175).
  • praetore-mcp dashboard: /favicon.ico is answered with 204 instead of
    404, so the browser console shows no error. Only GET on loopback, as for
    the other paths (#175).
  • praetore-safety-client: the non-blocking latency tests no longer fail on
    a loaded machine; a slow send still fails them (#175).
  • console: keep the operator language chosen during the first catalog
    load.
    If the operator changed language while that catalog request was
    still in flight, the first load could overwrite the choice and put the
    page back in Spanish (#161).
  • console: the package language test builds every download at one fixed
    instant
    , so the byte-for-byte comparison no longer fails when two
    builds straddle a second (#171).