# Arcstone MCP Sidecar

> Arcstone MCP Sidecar is an open-source MCP server for security. Experimental Rust boundary that blocks side effects without single-use authorization. It is available on CLI, Windows and self-hosted.

- **Kind:** MCP server
- **Pricing:** Open source
- **Platforms:** CLI, Windows, self-hosted
- **Repository:** https://github.com/trencinodin-stack/arcstone-mcp-sidecar
- **MCP Registry name:** io.github.trencinodin-stack/arcstone-mcp-sidecar
- **Categories:** [security](https://ai-powered.com/categories/security), [agent tooling](https://ai-powered.com/categories/agent-tooling)
- **Listing updated:** 2026-11-18

## About

This repository is a Rust implementation of a frozen v0.1 experimental specification for an execution boundary. It tests whether a deterministic downstream gate can stop an untrusted or nondeterministic producer from triggering a protected side effect unless a boundary-controlled authorization has been satisfied. The README labels it experimental, downstream, non-canonical and bounded-evidence, and says v0.1 does not require MCP, network APIs, signatures or policy engines.

State lives in a local runtime directory with issued and consumed authorization records, a protected effect file and per-run evidence folders. A single-use claim is made by atomically creating a file in the consumed folder, so replaying the same request is denied. The command-line tool `arcstone-exec` offers init, issue, execute and inspect commands, and a request names an authorization ID, action, resource ID and hex payload.

The authors report a separate Windows experiment with distinct producer and authority accounts and explicit ACL separation. Direct bypass of the protected resource, direct actuator bypass and forged authorization issuance all passed under the tested configuration. The README stresses that this does not establish general sandbox security or production authorization security.

It suits security researchers and developers exploring deterministic gating of agent or script side effects. The repo also ships machine-readable manifests and an AGENTS.md for automated traversal.

## Features

- **Single-use authorization:** Each issued authorization can lead to at most one protected actuation, enforced by atomic creation of a claim file.
- **No authorization, no effect:** Without a valid authorization the boundary performs zero protected actuation, and an untrusted producer cannot reach the protected resource directly.
- **Replay denial:** Re-submitting an already consumed request is denied before any second actuation attempt.
- **CLI workflow:** The arcstone-exec tool provides init, issue, execute and inspect commands for working with a local runtime root.
- **Separated state model:** Authorization lifecycle, gate decision, actuation result and observed protected effect are kept as distinct records.
- **Per-run evidence:** Each execution writes to its own evidence folder identified by a run ID.
- **Machine-readable manifests:** JSON manifests, a policy file and AGENTS.md let automated tools navigate and verify the repo.

## Good for

- Studying how to gate protected side effects behind explicit authorization
- Reproducing the bounded Windows ACL authority-separation experiment
- Testing replay protection for single-use authorizations
- Prototyping a deterministic execution gate in front of untrusted agent output
- Using as a reference for research on execution-boundary invariants

## FAQ

### Is this production-ready?

No. The README describes it as experimental, version 0.1.0, and says it makes no claim of production authorization security.

### How is single use enforced?

The consumed claim file is created with create_new(true), an atomic local reservation, so a replayed request finds the claim already present and is denied.

### How do I build it?

Run cargo build and cargo test, or on Windows run scripts\windows\verify.cmd.

### Does it actually use MCP?

The README says v0.1 does not require or claim MCP, although the registry entry describes it as a reference MCP sidecar.

### What did the Windows experiment show?

Under the tested ACL configuration with separate producer and authority accounts, direct resource bypass, direct actuator bypass and forged authorization issuance all passed.

### Is Arcstone MCP Sidecar free?

Yes. Arcstone MCP Sidecar is open source, so you can use and self-host it for free.

### What are the best alternatives to Arcstone MCP Sidecar?

The closest alternatives to Arcstone MCP Sidecar are AtlasClose Governance Demo, Archytan Lite MCP gate, signet-eval, Runeward and DeadBolt by NextEleven.

## Where this comes from

- Description: written from the project's README and its MCP Registry entry.

## Alternatives

- [AtlasClose Governance Demo](https://ai-powered.com/mcp/atlasclose-governance-demo): AtlasClose Governance Demo is an MCP server for security.
- [Archytan Lite MCP gate](https://ai-powered.com/mcp/archytan-lite-mcp-gate): Archytan Lite MCP gate is an open-source MCP server for security.
- [signet-eval](https://ai-powered.com/mcp/signet-eval): signet-eval is an open-source MCP server for security.
- [Runeward](https://ai-powered.com/mcp/runeward): Runeward is an open-source MCP server for developer tools.
- [DeadBolt by NextEleven](https://ai-powered.com/mcp/deadbolt-by-nexteleven): DeadBolt by NextEleven is an open-source MCP server for security.
- [Fathom](https://ai-powered.com/mcp/fathom-2): Fathom is an open-source MCP server for security.
- [BlackRoad](https://ai-powered.com/mcp/blackroad): BlackRoad is an MCP server for agent tooling.
- [Approval Gate MCP](https://ai-powered.com/mcp/approval-gate-mcp): Approval Gate MCP is an open-source MCP server for security.

---
Source: https://ai-powered.com/mcp/arcstone-mcp-sidecar
