# dcl_pipeline_start

SESSION Management ($0.05). Generates a new pipeline_id and returns session metadata (scope, expiry, initial drift_mode) for organizing a series of related checks under one identifier. Note: this call does not currently link the returned pipeline_id to later evaluate_* calls — there is no server-side session state that ties subsequent audits back to it; it is an identifier/timestamp issuer, not an active tracking session. Use this to obtain a shared reference ID for your own client-side grouping of a multi-step audit sequence; do not rely on it to automatically aggregate drift across calls.

Agent View of the PolicyLayer registry record for `dcl_pipeline_start`. HTML page: https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-pipeline-start

## Facts

- Tool: `dcl_pipeline_start`
- Server: Dcl Trust Oracle (`https://mcp.fronesislabs.com/mcp`) — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle.md
- Homepage: https://github.com/Fronesis-Labs/dcl-webhook
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 3 (1 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `scope` | string | no | Scope label for the session. |
| `agent_id` | string | yes | Identifier of the agent that owns this session. |
| `ttl_seconds` | integer | no | Session time-to-live, in seconds. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "dcl_pipeline_start",
    "arguments": {
      "agent_id": "<agent_id>"
    }
  }
}
```

## Why dcl_pipeline_start is rated High

dcl_pipeline_start triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

## Use case

AI agents invoke dcl_pipeline_start to trigger actions in Dcl Trust Oracle. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Dcl Trust Oracle:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "dcl_pipeline_start": {
      "limits": [
        {
          "counter": "dcl_pipeline_start_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Dcl Trust Oracle (17)

- `dcl_evaluate_strict` — Destructive — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-strict.md
- `dcl_evaluate_jailbreak_crypto` — Execute — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-jailbreak-crypto.md
- `dcl_evaluate_output_sanitizer` — Execute — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-output-sanitizer.md
- `dcl_evaluate_trade` — Financial — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-trade.md
- `dcl_audit_decode` — Read — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-audit-decode.md
- `dcl_audit_decode_deep` — Read — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-audit-decode-deep.md
- `dcl_evaluate_batch` — Read — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-batch.md
- `dcl_evaluate_fast` — Read — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-fast.md
- `dcl_evaluate_jailbreak` — Read — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-jailbreak.md
- `dcl_evaluate_mev` — Read — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-mev.md
- `dcl_evaluate_pii` — Read — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-pii.md
- `dcl_evaluate_quality` — Read — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-quality.md
- `dcl_evaluate_safety` — Read — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-safety.md
- `dcl_evaluate_secrets` — Read — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-secrets.md
- `dcl_evaluate_wallet` — Read — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-wallet.md
- `dcl_commit` — Write — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-commit.md
- `dcl_evaluate_signal` — Write — https://policylayer.com/tools/com-fronesislabs-dcl-trust-oracle/dcl-evaluate-signal.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-fronesislabs-dcl-trust-oracle · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-fronesislabs-dcl-trust-oracle