Product tour · PR Review & Auto-Fix

See how Tokynd Setright works — end to end

Security review that ends in a merge-ready patch, not another ticket. Follow one pull request from the moment it lands to a verified, evidenced close.

STEP 01

A pull request lands

A change touches agent code, an MCP config, a prompt, or a RAG pipeline — plus the spec it claims to implement.

STEP 02

Review, in the PR

Setright reviews the diff like a senior security colleague: over-scoped tools, prompt-injection surface, RAG permission bleed, secrets and machine identities in code — every finding cited to the line and the rule.

STEP 03

A merge-ready patch

For the finding kinds it covers, Setright generates the complete PR: the fix diff, the tests, the spec check, and the PR body. Nothing is left as a ticket for a human to translate.

STEP 04

The human gate, then proof

The agent owner approves and merges — Setright never merges on its own. The merged state is re-scanned, the closure verified, and the evidence flows to Dossier.

Watch it run

The same review the homepage runs live, walked stage by stage: one finding, its fix, and the verified close.

acme/support-agent · PR #482tokynd
Highmcp/tools.json · server: crm-lookup

MCP tool granted write scope it never uses

The crm-lookup server holds crm.records.write and crm.records.delete, but the agent only calls read paths. Reachability analysis confirms no write path is exercised.

Control SOC 2 CC6.1Framework OWASP MCP Top 10Reachable yes — tool layer
Fix proposedsetright-output/fix-482 · 2 files changed

The smallest patch that closes the finding

// mcp/tools.json — scope the server to what the agent uses - "scopes": ["crm.records.read", "crm.records.write", "crm.records.delete"] + "scopes": ["crm.records.read"] + "identity": "tokynd://agent/support/crm-lookup (15-min token)" // prompts/triage.md — bind tool calls to the approved spec + tool_policy: spec://support-agent/v3#tools.read-only
Tests 41 passedSpec check v3 ✓Human gate approval required
✓

Patch approved — the owner reviewed the patch and merged it at the human gate — the merge is recorded

✓

Identity re-issued — the long-lived key is retired; a scoped 15-minute token is provisioned by Tokynd Namesake

✓

Finding re-verified — re-scan of the merged state: the exposure is closed at the source

✓

Control evidence logged — the SOC 2 CC6.1 / ISO 42001 evidence pack is updated automatically

What comes out of the run

Per pull request

InputA pull request touching agent code, MCP, prompts, or RAG — and its spec
ReviewFindings cited to line and rule, with reachability — not a raw scanner dump
OutputA merge-ready PR: fix diff, tests, spec check, and body
ProofVerified closure on re-scan, logged as control evidence in Dossier
Available nowReview commenting and opening PRs directly in your repos roll out with design partners.
← All product tours Book a working session