# dials_deployWorkflow

Save a normalized workflow and enabled routing descriptor (POST /v1/dials/workflows/deploy) [service status: unverified]

Agent View of the PolicyLayer registry record for `dials_deployWorkflow`. HTML page: https://policylayer.com/tools/lifesi-genesis-mcp/dials-deployworkflow

## Facts

- Tool: `dials_deployWorkflow`
- Server: Genesis (`@lifesi/genesis-mcp`) — https://policylayer.com/tools/lifesi-genesis-mcp.md
- Install: `npx -y @lifesi/genesis-mcp`
- Homepage: https://www.npmjs.com/package/@lifesi/genesis-mcp
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `body` | object | yes | Upsert by scoped workflow ID. Backend supplies deployed status, stable route ID and enabled routing descriptor. This is persisted configuration, not runtime/tel |

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": "dials_deployWorkflow",
    "arguments": {
      "body": {}
    }
  }
}
```

## Why dials_deployWorkflow is rated High

dials_deployWorkflow 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.

Risk signals: Accepts raw HTML/template content (body) · High parameter count (27 properties)

## Use case

AI agents invoke dials_deployWorkflow to trigger actions in Genesis. 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 Genesis:

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

## Other tools on Genesis (251)

- `beacons_revokeBridgeDevice` — Destructive — https://policylayer.com/tools/lifesi-genesis-mcp/beacons-revokebridgedevice.md
- `dials_deleteNumber` — Destructive — https://policylayer.com/tools/lifesi-genesis-mcp/dials-deletenumber.md
- `fleets_cancelTask` — Destructive — https://policylayer.com/tools/lifesi-genesis-mcp/fleets-canceltask.md
- `fleets_deleteConnection` — Destructive — https://policylayer.com/tools/lifesi-genesis-mcp/fleets-deleteconnection.md
- `flocks_revokeNode` — Destructive — https://policylayer.com/tools/lifesi-genesis-mcp/flocks-revokenode.md
- `flocks_rotateNodeCredential` — Destructive — https://policylayer.com/tools/lifesi-genesis-mcp/flocks-rotatenodecredential.md
- `hives_cancel_deployment` — Destructive — https://policylayer.com/tools/lifesi-genesis-mcp/hives-cancel-deployment.md
- `hives_delete_bucket` — Destructive — https://policylayer.com/tools/lifesi-genesis-mcp/hives-delete-bucket.md
- `hives_delete_cron` — Destructive — https://policylayer.com/tools/lifesi-genesis-mcp/hives-delete-cron.md
- `hives_delete_deployment` — Destructive — https://policylayer.com/tools/lifesi-genesis-mcp/hives-delete-deployment.md
- `hives_delete_dlq_native_queue` — Destructive — https://policylayer.com/tools/lifesi-genesis-mcp/hives-delete-dlq-native-queue.md
- `hives_delete_function` — Destructive — https://policylayer.com/tools/lifesi-genesis-mcp/hives-delete-function.md
- `hives_delete_native_queue` — Destructive — https://policylayer.com/tools/lifesi-genesis-mcp/hives-delete-native-queue.md
- `hives_delete_native_topic` — Destructive — https://policylayer.com/tools/lifesi-genesis-mcp/hives-delete-native-topic.md
- `hives_delete_object` — Destructive — https://policylayer.com/tools/lifesi-genesis-mcp/hives-delete-object.md
- `hives_delete_object_by_key` — Destructive — https://policylayer.com/tools/lifesi-genesis-mcp/hives-delete-object-by-key.md
- `hives_delete_secret` — Destructive — https://policylayer.com/tools/lifesi-genesis-mcp/hives-delete-secret.md
- `hives_delete_volume` — Destructive — https://policylayer.com/tools/lifesi-genesis-mcp/hives-delete-volume.md
- `hives_detach_context_project` — Destructive — https://policylayer.com/tools/lifesi-genesis-mcp/hives-detach-context-project.md
- `hives_marketplace_uninstall` — Destructive — https://policylayer.com/tools/lifesi-genesis-mcp/hives-marketplace-uninstall.md
- `hives_purge_dlq_native_queue` — Destructive — https://policylayer.com/tools/lifesi-genesis-mcp/hives-purge-dlq-native-queue.md
- `hives_purge_native_queue` — Destructive — https://policylayer.com/tools/lifesi-genesis-mcp/hives-purge-native-queue.md
- `hives_remove_native_queue_consumer` — Destructive — https://policylayer.com/tools/lifesi-genesis-mcp/hives-remove-native-queue-consumer.md
- `hives_unsubscribe_native_topic` — Destructive — https://policylayer.com/tools/lifesi-genesis-mcp/hives-unsubscribe-native-topic.md
- `iam_revokeApiKey` — Destructive — https://policylayer.com/tools/lifesi-genesis-mcp/iam-revokeapikey.md
- `relays_deleteRecord` — Destructive — https://policylayer.com/tools/lifesi-genesis-mcp/relays-deleterecord.md
- `runner_cancelJob` — Destructive — https://policylayer.com/tools/lifesi-genesis-mcp/runner-canceljob.md
- `fleets_launchAgent` — Execute — https://policylayer.com/tools/lifesi-genesis-mcp/fleets-launchagent.md
- `fleets_startInstance` — Execute — https://policylayer.com/tools/lifesi-genesis-mcp/fleets-startinstance.md
- `fleets_stopAgent` — Execute — https://policylayer.com/tools/lifesi-genesis-mcp/fleets-stopagent.md
- …and 221 more: https://policylayer.com/tools/lifesi-genesis-mcp.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=lifesi-genesis-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/lifesi-genesis-mcp