reef-mcp 0.1.0__tar.gz

reef_mcp-0.1.0/.gitignore

@@ -0,0 +1,237 @@
+__pycache__/
+*.py[cod]
+*.egg-info/
+.venv/
+dist/
+build/
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.coverage
+*.db
+*.db-journal
+
+# Signing keys (made on first use)
+*.key
+
+# --- GitHub's Python template (from the repo's first commit) ---
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+*.lcov
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# uv
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi/*
+!.pixi/config.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule*
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs/Zensical documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore that
+#   can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, you
+#   could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml

reef_mcp-0.1.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.

reef_mcp-0.1.0/PKG-INFO

@@ -0,0 +1,116 @@
+Metadata-Version: 2.5
+Name: reef-mcp
+Version: 0.1.0
+Summary: A grant-shaped MCP gateway: agents see and call only what their Trellis grant allows.
+Project-URL: Homepage, https://github.com/FatherBrian/trellis/tree/main/reef
+Project-URL: Issues, https://github.com/FatherBrian/trellis/issues
+Author: Trellis contributors
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: access-control,ai-agents,audit,gateway,mcp
+Classifier: Development Status :: 2 - Pre-Alpha
+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: Programming Language :: Python :: 3.13
+Classifier: Topic :: Security
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Requires-Dist: anyio>=4
+Requires-Dist: mcp<3,>=2.3
+Requires-Dist: trellisd<0.2,>=0.1.0
+Requires-Dist: uvicorn>=0.30
+Description-Content-Type: text/markdown
+
+# Reef
+
+Reef is the door in front of your MCP servers. An agent connects once, with its Trellis
+grant token, and sees only the tools its grant allows. Every call it makes is decided by
+Trellis's three checks and written to the Trellis ledger before anything is forwarded.
+
+Package: `reef-mcp`. It depends on [`trellisd`](https://github.com/FatherBrian/trellis/blob/main/README.md) and runs Trellis in the same
+process.
+
+```
+pip install reef-mcp
+reef demo the-door
+```
+
+## What it does
+
+| | A persona-based gateway | Reef |
+|---|---|---|
+| Tool list | A fixed bundle per persona | Built per request from what the grant allows |
+| A tool outside the grant | Listed, then fails | Never listed; a call is denied at the door |
+| Downstream credentials | A secret per server, often the agent's | Per server: the person's own token (obo), the agent's own (agent), or a service credential only Reef holds (brokered) |
+| Masks and row filters | The server's problem | Applied by Reef to the result, and passed to the server in `_meta` so it can push them down |
+| Audit | Per server, if at all | Every list and call in one hash-chained ledger |
+
+On `tools/list`, Reef runs the three checks for every tool it fronts (without a ledger
+entry each) and writes one `tools.listed` event naming what it showed and what it hid.
+
+On `tools/call`:
+
+1. Trellis decides. The decision event is written first; if it can't be, the answer is a deny.
+2. A deny returns the check that refused and who to ask: the contract's owner, the agent's
+   owner, or the person who gave the grant. Reef records that it blocked the call, and
+   nothing reaches the server.
+3. Reef gets the credential the server's mode calls for. The ledger records the exchange,
+   never the token.
+4. Reef writes the enforcement event, and forwards only once that write succeeds.
+5. It masks columns and filters rows in the result, and writes the outcome before the
+   agent sees it. A result it can't record, or can't apply the obligations to, is held back.
+
+`trellisd trace <event>` shows a decision together with what the door did with it.
+
+## Configure
+
+`reef.yaml` lists the servers behind Reef:
+
+```yaml
+reef:
+  servers:
+    ledger:
+      url: https://ledger.internal/mcp
+      credential: obo              # the person's own token, exchanged at their IdP
+      audience: ledger-mcp
+      tools:
+        journal_entries: {action: query}
+        post_adjustment: {action: write}
+    hr:
+      url: https://hr.internal/mcp
+      credential: brokered         # a service credential Reef holds
+      credential_env: REEF_HR_TOKEN
+      tools:
+        headcount: {action: read}
+        payroll: {action: read}
+```
+
+Each tool's address is `mcp://<server>/<tool>` unless it names another `resource`. A
+Trellis contract binds that address, so the contract says what the tool is, who may use it
+and what gets masked. A tool no contract binds is denied and never listed; a tool the
+server offers and `reef.yaml` doesn't name is hidden.
+
+Agents see each tool as `<server>_<tool>`, a name every MCP client accepts.
+
+```
+reef serve --config reef.yaml --trellis trellis/ --db postgresql://... \
+    --key trellis.key --trellis-port 8180
+```
+
+Agents get their grant token from Trellis's token endpoint (`POST /token`) and send it
+to Reef as `Authorization: Bearer <grant token>`. `--trellis-port` serves that endpoint
+from Reef's own process, which obo mode needs: the person's sign-in is held in memory
+only, so the endpoint that takes it and the door that uses it must be one process.
+
+For trying it out, `reef sample ledger|hr` runs the sample MCP servers, and
+[quickstart/](https://github.com/FatherBrian/trellis/blob/main/quickstart/README.md) runs the whole thing with `docker compose up`.
+
+## Limits in v0.1
+
+- Trellis runs inside Reef. A Reef in front of a remote Trellis, over AuthZEN, comes later.
+- Reef applies masks and row filters to results shaped as rows: a list of objects, or an
+  object holding one. Any other shape, when there's something to apply, is held back.
+- The person's sign-in is held in memory for obo mode, so a restart means signing in again.

reef_mcp-0.1.0/README.md

@@ -0,0 +1,90 @@
+# Reef
+
+Reef is the door in front of your MCP servers. An agent connects once, with its Trellis
+grant token, and sees only the tools its grant allows. Every call it makes is decided by
+Trellis's three checks and written to the Trellis ledger before anything is forwarded.
+
+Package: `reef-mcp`. It depends on [`trellisd`](https://github.com/FatherBrian/trellis/blob/main/README.md) and runs Trellis in the same
+process.
+
+```
+pip install reef-mcp
+reef demo the-door
+```
+
+## What it does
+
+| | A persona-based gateway | Reef |
+|---|---|---|
+| Tool list | A fixed bundle per persona | Built per request from what the grant allows |
+| A tool outside the grant | Listed, then fails | Never listed; a call is denied at the door |
+| Downstream credentials | A secret per server, often the agent's | Per server: the person's own token (obo), the agent's own (agent), or a service credential only Reef holds (brokered) |
+| Masks and row filters | The server's problem | Applied by Reef to the result, and passed to the server in `_meta` so it can push them down |
+| Audit | Per server, if at all | Every list and call in one hash-chained ledger |
+
+On `tools/list`, Reef runs the three checks for every tool it fronts (without a ledger
+entry each) and writes one `tools.listed` event naming what it showed and what it hid.
+
+On `tools/call`:
+
+1. Trellis decides. The decision event is written first; if it can't be, the answer is a deny.
+2. A deny returns the check that refused and who to ask: the contract's owner, the agent's
+   owner, or the person who gave the grant. Reef records that it blocked the call, and
+   nothing reaches the server.
+3. Reef gets the credential the server's mode calls for. The ledger records the exchange,
+   never the token.
+4. Reef writes the enforcement event, and forwards only once that write succeeds.
+5. It masks columns and filters rows in the result, and writes the outcome before the
+   agent sees it. A result it can't record, or can't apply the obligations to, is held back.
+
+`trellisd trace <event>` shows a decision together with what the door did with it.
+
+## Configure
+
+`reef.yaml` lists the servers behind Reef:
+
+```yaml
+reef:
+  servers:
+    ledger:
+      url: https://ledger.internal/mcp
+      credential: obo              # the person's own token, exchanged at their IdP
+      audience: ledger-mcp
+      tools:
+        journal_entries: {action: query}
+        post_adjustment: {action: write}
+    hr:
+      url: https://hr.internal/mcp
+      credential: brokered         # a service credential Reef holds
+      credential_env: REEF_HR_TOKEN
+      tools:
+        headcount: {action: read}
+        payroll: {action: read}
+```
+
+Each tool's address is `mcp://<server>/<tool>` unless it names another `resource`. A
+Trellis contract binds that address, so the contract says what the tool is, who may use it
+and what gets masked. A tool no contract binds is denied and never listed; a tool the
+server offers and `reef.yaml` doesn't name is hidden.
+
+Agents see each tool as `<server>_<tool>`, a name every MCP client accepts.
+
+```
+reef serve --config reef.yaml --trellis trellis/ --db postgresql://... \
+    --key trellis.key --trellis-port 8180
+```
+
+Agents get their grant token from Trellis's token endpoint (`POST /token`) and send it
+to Reef as `Authorization: Bearer <grant token>`. `--trellis-port` serves that endpoint
+from Reef's own process, which obo mode needs: the person's sign-in is held in memory
+only, so the endpoint that takes it and the door that uses it must be one process.
+
+For trying it out, `reef sample ledger|hr` runs the sample MCP servers, and
+[quickstart/](https://github.com/FatherBrian/trellis/blob/main/quickstart/README.md) runs the whole thing with `docker compose up`.
+
+## Limits in v0.1
+
+- Trellis runs inside Reef. A Reef in front of a remote Trellis, over AuthZEN, comes later.
+- Reef applies masks and row filters to results shaped as rows: a list of objects, or an
+  object holding one. Any other shape, when there's something to apply, is held back.
+- The person's sign-in is held in memory for obo mode, so a restart means signing in again.

reef_mcp-0.1.0/examples/the-door/reef.yaml

@@ -0,0 +1,19 @@
+# Reef: one MCP endpoint in front of two servers. Agents connect with their Trellis grant
+# token and see only the tools their grant allows. `reef demo the-door` starts both sample
+# servers and fills in their URLs.
+reef:
+  servers:
+    ledger:
+      url: http://127.0.0.1:9101/mcp
+      credential: obo              # the person's own token, exchanged for this audience
+      audience: ledger-mcp
+      tools:
+        journal_entries: {action: query}
+        post_adjustment: {action: write}
+    hr:
+      url: http://127.0.0.1:9102/mcp
+      credential: brokered         # a service credential Reef holds; agents never see it
+      credential_env: REEF_HR_TOKEN
+      tools:
+        headcount: {action: read}
+        payroll: {action: read}

reef_mcp-0.1.0/examples/the-door/trellis/agents.yaml

@@ -0,0 +1,17 @@
+# Each agent's owner sets its ceiling: the most it may ever touch, whoever it works for.
+agents:
+  report-bot:
+    owner: dana@example.com
+    description: Drafts finance reports.
+    identities: [local:report-bot]
+    ceiling:
+      actions: [read, query]
+      # confidential covers the levels under it (public, internal) too.
+      tags: [finance, hr, pii, confidential]
+  people-bot:
+    owner: hr-lead@example.com
+    description: Answers HR questions.
+    identities: [local:people-bot]
+    ceiling:
+      actions: [read, query]
+      tags: [hr, pii, confidential]