Governance layer for agentic AI — signed, verifiable receipts for every agent action.
Deterministic policy control for autonomous systems.
Kasbah Core is a minimal control plane that sits between AI agents and execution: it evaluates intent, enforces tool gates, and writes an append-only audit log.
This repo ships a runnable prototype for security engineers and CTOs.
docker compose up --build
---
## 🔐 Minimal real API example (no demo, no UI)
This is a real Kasbah-Core runtime flow.
No simulation. No frontend. No policy-only logic.
STEP 1 — Ask Kasbah if an action is allowed
curl -s http://localhost:8002/api/rtp/decide \
-H "Content-Type: application/json" \
-H "Authorization: Bearer DEV_KEY" \
-d '{
"agent_id": "support-bot",
"tool_name": "db.query",
"signals": {
"consistency": 0.95,
"context": 0.90
}
}'
Example response:
{
"decision": "ALLOW",
"ticket": {
"jti": "5a3bde1e887e000116e8943663b5088d",
"expires_at": 1770307384
}
}
STEP 2 — Execute the action using the issued ticket
curl -s http://localhost:8002/api/rtp/consume \
-H "Content-Type: application/json" \
-d '{
"ticket": "5a3bde1e887e000116e8943663b5088d",
"tool_name": "db.query",
"usage": { "tokens": 120 }
}'
Response:
{ "status": "ALLOWED" }
STEP 3 — Replay the same ticket (blocked by Kasbah)
curl -s http://localhost:8002/api/rtp/consume \
-H "Content-Type: application/json" \
-d '{
"ticket": "5a3bde1e887e000116e8943663b5088d",
"tool_name": "db.query"
}'
Response:
{
"status": "DENIED",
"reason": "replay_detected"
}
This denial is stateful and irreversible.
Tickets are single-use, tool-bound, time-bound, and verified at runtime.
---
## 🔐 Minimal real API example (no demo, no UI)
This is a real Kasbah-Core runtime flow.
No simulation. No frontend. No policy-only logic.
STEP 1 — Ask Kasbah if an action is allowed
curl -s http://localhost:8002/api/rtp/decide \
-H "Content-Type: application/json" \
-H "Authorization: Bearer DEV_KEY" \
-d '{
"agent_id": "support-bot",
"tool_name": "db.query",
"signals": {
"consistency": 0.95,
"context": 0.90
}
}'
Example response:
{
"decision": "ALLOW",
"ticket": {
"jti": "5a3bde1e887e000116e8943663b5088d",
"expires_at": 1770307384
}
}
STEP 2 — Execute the action using the issued ticket
curl -s http://localhost:8002/api/rtp/consume \
-H "Content-Type: application/json" \
-d '{
"ticket": "5a3bde1e887e000116e8943663b5088d",
"tool_name": "db.query",
"usage": { "tokens": 120 }
}'
Response:
{ "status": "ALLOWED" }
STEP 3 — Replay the same ticket (blocked by Kasbah)
curl -s http://localhost:8002/api/rtp/consume \
-H "Content-Type: application/json" \
-d '{
"ticket": "5a3bde1e887e000116e8943663b5088d",
"tool_name": "db.query"
}'
Response:
{
"status": "DENIED",
"reason": "replay_detected"
}
This denial is stateful and irreversible.
Tickets are single-use, tool-bound, time-bound, and verified at runtime.
## Moats / Security posture
See `docs/MOATS_REGISTRY.md` for the authoritative list of implemented moats, evidence, and explicit non-goals.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @yobekasbah/mcp-serverMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-al-adnane-kasbah-mcp": {
"command": "npx",
"args": [
"-y",
"@yobekasbah/mcp-server"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@yobekasbah/mcp-servernpmio.github.Al-Adnane/kasbah-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.