Independent by design · no pay-to-rank placements  · How we evaluate tools →
Anclum Submit
D

dvchinx/countersign

Independent directory — not the official site. Details below come from the project's public repository.

Runtime guardrails for Spring AI agents: policy-enforced, human-approved, signed tool calls (incl.

Before you install: no copy-paste command · license Apache-2.0

First step: nothing runnable here yet - start from the repository: https://github.com/dvchinx/countersign

updated 2026-11-19
View on GitHub ↗Direct link · no redirect page
Star count
0 ★ · dvchinx/countersign · read from the GitHub search API · (checked 2026-11-19 20:00:48)
Source
read directly from its GitHub page · type: open-source project
Harvest history
first seen 2026-11-20 · last seen 2026-11-20 · seen 1× · listed by 1 sources
Score
score 103 · 1 sources · repo
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: Open Source. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository dvchinx/countersign;first catalogued 2026-11-20;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.
README excerpt (English, untranslated) · Read the full README on GitHub →

Countersign

Excerpted from the repository README (abridged)

Your agent proposes. Countersign decides.
Runtime guardrails for Spring AI agents: policy-enforced, human-approved, signed tool calls (incl. MCP).
Fail-closed, auditable. One starter dependency, no Python sidecar.
English · Español
In law, a countersignature is the second signature that makes a document valid.
Countersign adds that second signature to your AI agent's actions: every tool call the model
proposes is checked against your policies, sent to a human when it needs one, and recorded in an
Ed25519-signed, hash-chained receipt before anything runs.
Think of it as Spring Security for agent tool calls. It works with Spring AI @Tool methods,
ToolCallbacks and MCP tools, and you don't have to change your tools.
## Demo
> The recorded GIF ships with 0.1.0. This is what the banking-agent example shows:
The model never sees a stack trace. It gets a structured refusal it can explain to the user, and
you get a receipt you can verify later.
## Quickstart
> Pre-alpha: this is the API we are building toward 0.1.0. Watch the repo to know when it lands.
1. Add the starter
xml
io.github.dvchinx
countersign-spring-boot-starter
0.1.0
2. Write a few policies in application.yml
yaml
countersign:
default-decision: deny # fail closed: anything not allowed is blocked
policies:
id: no-destructive-sql
tools: ["db."]
when: "#args['query'] matches '(?i).\\b(drop|truncate|delete)\\b.'"
decision: deny
id: transfers-need-approval
tools: ["payments.transfer"]
when: "#args['amount'] > 1000"
decision: require-approval
3. That's it. Your existing tools are wrapped automatically:
java
@Tool(description = "Transfer money between accounts")
@RequiresApproval(reason = "Moves real money") // optional: per-tool policy as an annotation
public TransferResult transfer(String from, String to, BigDecimal amount) { ... }
On startup you'll see one line telling you Countersign is active and which default it uses.
## What happens on a tool call
1. Build a ToolInvocation: tool name, parsed arguments, principal, conversation id.
2. Evaluate it against your policies, in priority order. The first match wins; if nothing matches, the default (deny) applies.
3. Apply the decision: run the tool, refuse it, ask a human, or redact it.
4. Record a receipt: the decision, the matched policies, a keyed hash (HMAC-SHA256) of the arguments (never the raw values), the previous receipt's hash, and an Ed25519 signature.
5. Publish it to your AuditSink, along with Micrometer metrics and observations.
Enforcement happens where the tool runs, not in the list of tools sent to the model. A tool the
model was never offered, or one it was tricked into calling, still has to pass the policy engine.
## How it compares
Countersign does not filter prompts or model output. It governs actions. Use it alongside a
content filter, not instead of one.
| | Countersign | Prompt / output filters | Python guardrail sidecar | if checks inside each @Tool |
| Enforces at the tool call itself | ✅ | ❌ | ⚠️ depends on wiring | ✅ |
| Runs in your JVM, no extra service | ✅ | ✅ | ❌ | ✅ |
| Covers MCP tools | ✅ | ❌ | ⚠️ | ❌ (not your code) |
| Human approval built in | ✅ | ❌ | ⚠️ | ❌ roll your own |
| Signed, hash-chained audit trail | ✅ | ❌ | ❌ | ❌ |
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/en/s/dvchinx-countersign/)
Source
github · https://github.com/dvchinx/countersign
Browse by field
Open source
added
today

More entries

All 1,875 →

Filed under

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index