onetrust-api 1.3.6__tar.gz → 1.4.0__tar.gz

{onetrust_api-1.3.6/onetrust_api.egg-info → onetrust_api-1.4.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: onetrust-api
-Version: 1.3.6
+Version: 1.4.0
 Summary: OneTrust API + MCP Server + A2A Agent — 100% API coverage
 Author-email: Repository Maintainers <maintainers@knuckles.team>
 License: MIT
@@ -12,11 +12,11 @@ Classifier: Programming Language :: Python :: 3
 Requires-Python: >=3.12
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: scion-sdk[mcp]<0.7.0,>=0.6.4
+Requires-Dist: scion-sdk[mcp]<0.12,>=0.11.0
 Requires-Dist: python-dotenv>=1.2.4
 Requires-Dist: requests>=2.34.2
 Provides-Extra: mcp
-Requires-Dist: scion-sdk[mcp]<0.7.0,>=0.6.4; extra == "mcp"
+Requires-Dist: scion-sdk[mcp]<0.12,>=0.11.0; extra == "mcp"
 Provides-Extra: all
 Requires-Dist: onetrust-api[mcp]>=1.3.0; extra == "all"
 Provides-Extra: test
@@ -59,10 +59,10 @@ consent, data-governance, and risk platform.
 
 It provides **100% coverage of the OneTrust public API** — every operation across
 all **35 OpenAPI specifications** (~600 operations, 7 product areas) is exposed as
-both a typed client method and an action-routed MCP tool. The client, MCP tools,
-and a machine-readable coverage manifest are all **generated from the vendored
-OpenAPI specs** (`onetrust_api/specs/*.json`) by `scripts/generate_from_openapi.py`,
-and a coverage test asserts the three sets stay in lock-step.
+both a typed client method and its own typed MCP tool. The client and a
+machine-readable coverage manifest derive from the vendored OpenAPI specs
+(`onetrust_api/specs/*.json`), and a coverage test asserts the sets stay in
+lock-step.
 
 ### Key Features
 
@@ -275,8 +275,8 @@ _39 intent tool(s) · 0 operation(s). Call an operation as `act(action='<operati
 <!-- MCP-CONFIG-EXAMPLES:START -->
 
 > **Install the connector-focused `[mcp]` extra.** Examples use `onetrust-api[mcp]` to add
-> FastMCP / FastAPI through `scion-sdk[mcp]`; the required Agent Utilities core
-> still carries `epistemic-graph[full]`. The `[agent-runtime]` extra additionally
+> FastMCP / FastAPI through `scion-sdk[mcp]`; the required Meristem core
+> still carries `medulla`. The `[agent-runtime]` extra additionally
 > enables model orchestration.
 
 #### stdio Transport (local IDEs — Cursor, Claude Desktop, VS Code)
@@ -506,7 +506,7 @@ docker run -d \
 > The `:mcp` tag is the **MCP-serving image** (built from
 > `docker/Dockerfile --target mcp`, installing `onetrust-api[mcp]`). The default
 > the immutable agent image is the **full agent image** (`--target agent`, `onetrust-api[agent]`)
-> which also bundles the Pydantic AI agent and the epistemic-graph engine — use it
+> which also bundles the Pydantic AI agent and the medulla engine — use it
 > when the operator run `onetrust-agent` (the agent), not just the MCP server. See
 > [Container images](#container-images-mcp-vs-agent).
 
@@ -532,8 +532,8 @@ Pick the extra that matches what the operator want to run:
 
 | Extra | Installs | Use when |
 |-------|----------|----------|
-| `onetrust-api[mcp]` | Connector-focused MCP server (`scion-sdk[mcp]` — FastMCP/FastAPI + `epistemic-graph[full]`) | The operator only run the **MCP server** (smallest install / image) |
-| `onetrust-api[agent]` | Agent runtime (`scion-sdk[agent-runtime,logfire]` — model orchestration + `epistemic-graph[full]`) | The operator run the **integrated agent** |
+| `onetrust-api[mcp]` | Connector-focused MCP server (`scion-sdk[mcp]` — FastMCP/FastAPI + `medulla`) | The operator only run the **MCP server** (smallest install / image) |
+| `onetrust-api[agent]` | Agent runtime (`scion-sdk[agent-runtime,logfire]` — model orchestration + `medulla`) | The operator run the **integrated agent** |
 | `onetrust-api[all]` | Everything (`mcp` + `agent`) | Development / both surfaces |
 
 ```bash
@@ -553,8 +553,8 @@ One multi-stage `docker/Dockerfile` builds two right-sized images, selected by `
 
 | Image tag | Build target | Contents | Entrypoint |
 |-----------|--------------|----------|------------|
-| `example/onetrust-api:mcp` | `--target mcp` | `onetrust-api[mcp]` — **connector-focused**, includes `epistemic-graph[full]`; no model-orchestration stack | `onetrust-mcp` |
-| `example/onetrust-api@sha256:<digest>` | `--target agent` (default) | `onetrust-api[agent]` — **agent runtime**, model orchestration + `epistemic-graph[full]` | `onetrust-agent` |
+| `example/onetrust-api:mcp` | `--target mcp` | `onetrust-api[mcp]` — **connector-focused**, includes `medulla`; no model-orchestration stack | `onetrust-mcp` |
+| `example/onetrust-api@sha256:<digest>` | `--target agent` (default) | `onetrust-api[agent]` — **agent runtime**, model orchestration + `medulla` | `onetrust-agent` |
 
 ```bash
 docker build --target mcp   -t example/onetrust-api:mcp    docker/   # connector-focused MCP server
@@ -564,16 +564,16 @@ docker build --target agent -t example/onetrust-api:agent-local docker/   # agen
 `docker/mcp.compose.yml` runs the connector-focused `:mcp` server; `docker/agent.compose.yml` runs the
 agent (`immutable agent digest`) with a co-located `:mcp` sidecar.
 
-### Knowledge-graph database (`epistemic-graph`)
+### Knowledge-graph database (`medulla`)
 
-Both `[mcp]` and `[agent]` carry the **epistemic-graph** engine through the required
-Agent Utilities core dependency (`epistemic-graph[full]`). The `[mcp]` extra keeps
+Both `[mcp]` and `[agent]` carry the **medulla** engine through the required
+Meristem core dependency (`medulla`). The `[mcp]` extra keeps
 the server connector-focused; `[agent]` also enables model orchestration. Local
 deployments can use the bundled engine. For production or shared state, run
-**epistemic-graph as a dedicated database service** and configure the runtime to use it.
+**medulla as a dedicated database service** and configure the runtime to use it.
 Deployment recipes (single-node + Raft HA), connection configuration, and architecture
 diagrams are documented in the
-[epistemic-graph deployment guide](https://knuckles-team.github.io/epistemic-graph/deployment/).
+[medulla deployment guide](https://knuckles-team.github.io/medulla/deployment/).
 
 ## Environment Variables
 
@@ -600,17 +600,14 @@ starting point.
 | `HOST` | Bind host (HTTP transports) | `0.0.0.0` |
 | `PORT` | Bind port (HTTP transports) | `8000` |
 | `AUTH_TYPE` | MCP transport auth mode (`none`, …) | `none` |
-| `MCP_TOOL_MODE` | Tool surface: `condensed`, `verbose`, or `both` | `condensed` |
 | `MCP_ENABLED_TOOLS` / `MCP_DISABLED_TOOLS` | Comma-separated tool allow/deny list | — |
 | `MCP_ENABLED_TAGS` / `MCP_DISABLED_TAGS` | Comma-separated tag allow/deny list | — |
 | `FASTMCP_LOG_LEVEL` | FastMCP log level (e.g. `INFO`, `DEBUG`) | `INFO` |
 | `DEBUG` | Verbose logging | `False` |
 | `PYTHONUNBUFFERED` | Unbuffered stdout (recommended in containers) | `1` |
 
-### Tool toggles
-Each action-routed domain tool can be disabled individually via its `<DOMAIN>TOOL` toggle env
-var (set to `false`). The full list is in the [Available MCP Tools](#available-mcp-tools) table
-above (e.g. `INCIDENTSTOOL`, `DSARTOOL`, `CONSENT_RECEIPTSTOOL`, `ESGTOOL`).
+Every operation is its own tool. Use `MCP_ENABLED_TOOLS` / `MCP_DISABLED_TOOLS` or the tag
+lists above to narrow the surface.
 
 ### Telemetry & governance
 | Variable | Description | Default |

{onetrust_api-1.3.6 → onetrust_api-1.4.0}/README.md

@@ -31,10 +31,10 @@ consent, data-governance, and risk platform.
 
 It provides **100% coverage of the OneTrust public API** — every operation across
 all **35 OpenAPI specifications** (~600 operations, 7 product areas) is exposed as
-both a typed client method and an action-routed MCP tool. The client, MCP tools,
-and a machine-readable coverage manifest are all **generated from the vendored
-OpenAPI specs** (`onetrust_api/specs/*.json`) by `scripts/generate_from_openapi.py`,
-and a coverage test asserts the three sets stay in lock-step.
+both a typed client method and its own typed MCP tool. The client and a
+machine-readable coverage manifest derive from the vendored OpenAPI specs
+(`onetrust_api/specs/*.json`), and a coverage test asserts the sets stay in
+lock-step.
 
 ### Key Features
 
@@ -247,8 +247,8 @@ _39 intent tool(s) · 0 operation(s). Call an operation as `act(action='<operati
 <!-- MCP-CONFIG-EXAMPLES:START -->
 
 > **Install the connector-focused `[mcp]` extra.** Examples use `onetrust-api[mcp]` to add
-> FastMCP / FastAPI through `scion-sdk[mcp]`; the required Agent Utilities core
-> still carries `epistemic-graph[full]`. The `[agent-runtime]` extra additionally
+> FastMCP / FastAPI through `scion-sdk[mcp]`; the required Meristem core
+> still carries `medulla`. The `[agent-runtime]` extra additionally
 > enables model orchestration.
 
 #### stdio Transport (local IDEs — Cursor, Claude Desktop, VS Code)
@@ -478,7 +478,7 @@ docker run -d \
 > The `:mcp` tag is the **MCP-serving image** (built from
 > `docker/Dockerfile --target mcp`, installing `onetrust-api[mcp]`). The default
 > the immutable agent image is the **full agent image** (`--target agent`, `onetrust-api[agent]`)
-> which also bundles the Pydantic AI agent and the epistemic-graph engine — use it
+> which also bundles the Pydantic AI agent and the medulla engine — use it
 > when the operator run `onetrust-agent` (the agent), not just the MCP server. See
 > [Container images](#container-images-mcp-vs-agent).
 
@@ -504,8 +504,8 @@ Pick the extra that matches what the operator want to run:
 
 | Extra | Installs | Use when |
 |-------|----------|----------|
-| `onetrust-api[mcp]` | Connector-focused MCP server (`scion-sdk[mcp]` — FastMCP/FastAPI + `epistemic-graph[full]`) | The operator only run the **MCP server** (smallest install / image) |
-| `onetrust-api[agent]` | Agent runtime (`scion-sdk[agent-runtime,logfire]` — model orchestration + `epistemic-graph[full]`) | The operator run the **integrated agent** |
+| `onetrust-api[mcp]` | Connector-focused MCP server (`scion-sdk[mcp]` — FastMCP/FastAPI + `medulla`) | The operator only run the **MCP server** (smallest install / image) |
+| `onetrust-api[agent]` | Agent runtime (`scion-sdk[agent-runtime,logfire]` — model orchestration + `medulla`) | The operator run the **integrated agent** |
 | `onetrust-api[all]` | Everything (`mcp` + `agent`) | Development / both surfaces |
 
 ```bash
@@ -525,8 +525,8 @@ One multi-stage `docker/Dockerfile` builds two right-sized images, selected by `
 
 | Image tag | Build target | Contents | Entrypoint |
 |-----------|--------------|----------|------------|
-| `example/onetrust-api:mcp` | `--target mcp` | `onetrust-api[mcp]` — **connector-focused**, includes `epistemic-graph[full]`; no model-orchestration stack | `onetrust-mcp` |
-| `example/onetrust-api@sha256:<digest>` | `--target agent` (default) | `onetrust-api[agent]` — **agent runtime**, model orchestration + `epistemic-graph[full]` | `onetrust-agent` |
+| `example/onetrust-api:mcp` | `--target mcp` | `onetrust-api[mcp]` — **connector-focused**, includes `medulla`; no model-orchestration stack | `onetrust-mcp` |
+| `example/onetrust-api@sha256:<digest>` | `--target agent` (default) | `onetrust-api[agent]` — **agent runtime**, model orchestration + `medulla` | `onetrust-agent` |
 
 ```bash
 docker build --target mcp   -t example/onetrust-api:mcp    docker/   # connector-focused MCP server
@@ -536,16 +536,16 @@ docker build --target agent -t example/onetrust-api:agent-local docker/   # agen
 `docker/mcp.compose.yml` runs the connector-focused `:mcp` server; `docker/agent.compose.yml` runs the
 agent (`immutable agent digest`) with a co-located `:mcp` sidecar.
 
-### Knowledge-graph database (`epistemic-graph`)
+### Knowledge-graph database (`medulla`)
 
-Both `[mcp]` and `[agent]` carry the **epistemic-graph** engine through the required
-Agent Utilities core dependency (`epistemic-graph[full]`). The `[mcp]` extra keeps
+Both `[mcp]` and `[agent]` carry the **medulla** engine through the required
+Meristem core dependency (`medulla`). The `[mcp]` extra keeps
 the server connector-focused; `[agent]` also enables model orchestration. Local
 deployments can use the bundled engine. For production or shared state, run
-**epistemic-graph as a dedicated database service** and configure the runtime to use it.
+**medulla as a dedicated database service** and configure the runtime to use it.
 Deployment recipes (single-node + Raft HA), connection configuration, and architecture
 diagrams are documented in the
-[epistemic-graph deployment guide](https://knuckles-team.github.io/epistemic-graph/deployment/).
+[medulla deployment guide](https://knuckles-team.github.io/medulla/deployment/).
 
 ## Environment Variables
 
@@ -572,17 +572,14 @@ starting point.
 | `HOST` | Bind host (HTTP transports) | `0.0.0.0` |
 | `PORT` | Bind port (HTTP transports) | `8000` |
 | `AUTH_TYPE` | MCP transport auth mode (`none`, …) | `none` |
-| `MCP_TOOL_MODE` | Tool surface: `condensed`, `verbose`, or `both` | `condensed` |
 | `MCP_ENABLED_TOOLS` / `MCP_DISABLED_TOOLS` | Comma-separated tool allow/deny list | — |
 | `MCP_ENABLED_TAGS` / `MCP_DISABLED_TAGS` | Comma-separated tag allow/deny list | — |
 | `FASTMCP_LOG_LEVEL` | FastMCP log level (e.g. `INFO`, `DEBUG`) | `INFO` |
 | `DEBUG` | Verbose logging | `False` |
 | `PYTHONUNBUFFERED` | Unbuffered stdout (recommended in containers) | `1` |
 
-### Tool toggles
-Each action-routed domain tool can be disabled individually via its `<DOMAIN>TOOL` toggle env
-var (set to `false`). The full list is in the [Available MCP Tools](#available-mcp-tools) table
-above (e.g. `INCIDENTSTOOL`, `DSARTOOL`, `CONSENT_RECEIPTSTOOL`, `ESGTOOL`).
+Every operation is its own tool. Use `MCP_ENABLED_TOOLS` / `MCP_DISABLED_TOOLS` or the tag
+lists above to narrow the surface.
 
 ### Telemetry & governance
 | Variable | Description | Default |

{onetrust_api-1.3.6 → onetrust_api-1.4.0}/onetrust_api/api/_operation_manifest.py

@@ -27432,12 +27432,6 @@ OPERATIONS = [
                 "required": False,
                 "description": "number of days before the deadline when the reminder will be sent",
             },
-            {
-                "name": "action",
-                "type": "string",
-                "required": False,
-                "description": "risk action",
-            },
             {
                 "name": "probabilityLevelId",
                 "type": "integer",
@@ -27639,13 +27633,6 @@ OPERATIONS = [
                 "schema": {"type": "integer"},
                 "description": "number of days before the deadline when the reminder will be sent",
             },
-            {
-                "name": "action",
-                "in": "query",
-                "required": False,
-                "schema": {"type": "string"},
-                "description": "risk action",
-            },
             {
                 "name": "probabilityLevelId",
                 "in": "query",
@@ -28118,46 +28105,6 @@ OPERATIONS = [
             },
         ],
     },
-    {
-        "operation_id": "performRiskActionUsingPUT",
-        "domain": "it_risk_management",
-        "method": "perform_risk_action_using_put",
-        "action": "perform_risk_action_using_put",
-        "http": "PUT",
-        "path": "https://__HOSTNAME__/api/risk/v2/risks/{riskId}/actions/{action}",
-        "paginate": "none",
-        "summary": "Perform Risk Action",
-        "params": [
-            {
-                "name": "riskId",
-                "type": "string",
-                "required": True,
-                "description": "Unique identifier of the risk",
-            },
-            {
-                "name": "action",
-                "type": "string",
-                "required": True,
-                "description": "Action to perform on the risk",
-            },
-        ],
-        "parameters": [
-            {
-                "name": "riskId",
-                "in": "path",
-                "required": True,
-                "schema": {"type": "string"},
-                "description": "Unique identifier of the risk",
-            },
-            {
-                "name": "action",
-                "in": "path",
-                "required": True,
-                "schema": {"type": "string"},
-                "description": "Action to perform on the risk",
-            },
-        ],
-    },
     {
         "operation_id": "approveRiskUsingPUT",
         "domain": "it_risk_management",

{onetrust_api-1.3.6 → onetrust_api-1.4.0}/onetrust_api/api/api_client_it_risk_management.py

@@ -528,18 +528,6 @@ class OneTrustItRiskManagement(OneTrustApiBase):
             kwargs=kwargs,
         )
 
-    def perform_risk_action_using_put(self, **kwargs) -> Response:
-        """Perform Risk Action"""
-        return self._call(
-            http="PUT",
-            url_template="https://__HOSTNAME__/api/risk/v2/risks/{riskId}/actions/{action}",
-            path_params=["riskId", "action"],
-            query_params=[],
-            has_body=False,
-            paginate="none",
-            kwargs=kwargs,
-        )
-
     def approve_risk_using_put(self, **kwargs) -> Response:
         """Approve Risk"""
         return self._call(