Open Source · MCP
Protect the route, not the label.
RuleOak supports selected MCP stdio and Streamable HTTP paths. Capability metadata helps discovery, but it neither grants authority nor proves the external effect semantics of a tool.
Stdio boundary
MCP client ↔ RuleOak managed wrapper ↔ MCP servernode packages/cli/bin/ruleoak.js protect --setup --dry-run
node packages/cli/bin/ruleoak.js protect --setup --apply
node packages/cli/bin/ruleoak.js protect checkProtection states
READY_EFFECT_BOUNDARY
Interception is healthy and trusted postcondition semantics exist for the required route.
READY_POLICY_ONLY
Authorization is healthy but effect verification is incomplete.
ATTENTION
Route proof, configuration, evidence or unresolved state needs operator review.
Common mistakes
- assuming a client built-in is governed because one MCP server is governed;
- assuming all tools on a server share the same effect semantics;
- treating schema discovery as permission;
- treating transport success as the business postcondition;
- exposing a local proxy over a network without explicit auth/TLS controls.