# dry_run_endpoint

Validate an endpoint document without writing it. Returns either {ok: true, resolved: <Framework config slice>} or {ok: false, errors: {...}}. Pass endpointId to dry-run a PATCH against an existing endpoint; omit it to dry-run a create. Supply sample and/or answerSample to also run each target's mapping against a real payload and see what it produces, which field came from which node, and every rule that failed with the value that broke it. No DB write, no queue entry, no billing, and the payload is never sent anywhere.

Agent View of the PolicyLayer registry record for `dry_run_endpoint`. HTML page: https://policylayer.com/tools/dev-echorelay-management/dry-run-endpoint

## Facts

- Tool: `dry_run_endpoint`
- Server: EchoRelay (`https://mcp.echorelay.dev`) — https://policylayer.com/tools/dev-echorelay-management.md
- Homepage: https://github.com/https://mcp.echorelay.dev
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 5 (2 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `sample` | object | array | string | number | boolean | null | no | Optional: a request payload, shaped as one a caller would actually send, passed as JSON rather than as a string containing JSON. Every target carrying an outgoi |
| `lineKey` | string | yes | The line key. |
| `endpoint` | object | yes | Endpoint document (for create dry-run) or PATCH body (when endpointId is supplied). |
| `endpointId` | string | no | Optional: dry-run a PATCH against this endpoint UUID. |
| `answerSample` | object | array | string | number | boolean | null | no | Optional: an answer payload, shaped as one a target would actually return. Drives answerMapping the same way, as answerMappingEvaluation. It cannot be inferred |

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": "dry_run_endpoint",
    "arguments": {
      "lineKey": "<lineKey>",
      "endpoint": {}
    }
  }
}
```

## Why dry_run_endpoint is rated High

dry_run_endpoint 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 URL/endpoint input (endpoint) · Handles credentials or secrets (endpoint.targets[].auth) · Accepts raw HTML/template content (endpoint.targets[].mapping[].template) · High parameter count (56 properties) · Bulk/mass operation — affects multiple targets

## Use case

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

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

## Other tools on EchoRelay (77)

- `cancel_line_publish` — Destructive — https://policylayer.com/tools/dev-echorelay-management/cancel-line-publish.md
- `delete_credential` — Destructive — https://policylayer.com/tools/dev-echorelay-management/delete-credential.md
- `delete_endpoint` — Destructive — https://policylayer.com/tools/dev-echorelay-management/delete-endpoint.md
- `delete_line` — Destructive — https://policylayer.com/tools/dev-echorelay-management/delete-line.md
- `discard_dlq_entry` — Destructive — https://policylayer.com/tools/dev-echorelay-management/discard-dlq-entry.md
- `discard_draft_endpoint` — Destructive — https://policylayer.com/tools/dev-echorelay-management/discard-draft-endpoint.md
- `discard_line_draft` — Destructive — https://policylayer.com/tools/dev-echorelay-management/discard-line-draft.md
- `remove_member` — Destructive — https://policylayer.com/tools/dev-echorelay-management/remove-member.md
- `revoke_api_key` — Destructive — https://policylayer.com/tools/dev-echorelay-management/revoke-api-key.md
- `revoke_project_token` — Destructive — https://policylayer.com/tools/dev-echorelay-management/revoke-project-token.md
- `rollback_config` — Destructive — https://policylayer.com/tools/dev-echorelay-management/rollback-config.md
- `duplicate_line` — Execute — https://policylayer.com/tools/dev-echorelay-management/duplicate-line.md
- `cancel_subscription` — Financial — https://policylayer.com/tools/dev-echorelay-management/cancel-subscription.md
- `change_plan` — Financial — https://policylayer.com/tools/dev-echorelay-management/change-plan.md
- `downgrade_addon` — Financial — https://policylayer.com/tools/dev-echorelay-management/downgrade-addon.md
- `retry_dlq_entry` — Financial — https://policylayer.com/tools/dev-echorelay-management/retry-dlq-entry.md
- `start_subscription` — Financial — https://policylayer.com/tools/dev-echorelay-management/start-subscription.md
- `start_topup` — Financial — https://policylayer.com/tools/dev-echorelay-management/start-topup.md
- `subscribe_addon` — Financial — https://policylayer.com/tools/dev-echorelay-management/subscribe-addon.md
- `unsubscribe_addon` — Financial — https://policylayer.com/tools/dev-echorelay-management/unsubscribe-addon.md
- `default_endpoint_template` — Read — https://policylayer.com/tools/dev-echorelay-management/default-endpoint-template.md
- `get_billing` — Read — https://policylayer.com/tools/dev-echorelay-management/get-billing.md
- `get_config` — Read — https://policylayer.com/tools/dev-echorelay-management/get-config.md
- `get_dlq_entry` — Read — https://policylayer.com/tools/dev-echorelay-management/get-dlq-entry.md
- `get_endpoint` — Read — https://policylayer.com/tools/dev-echorelay-management/get-endpoint.md
- `get_key_policy` — Read — https://policylayer.com/tools/dev-echorelay-management/get-key-policy.md
- `get_line_draft` — Read — https://policylayer.com/tools/dev-echorelay-management/get-line-draft.md
- `get_metrics` — Read — https://policylayer.com/tools/dev-echorelay-management/get-metrics.md
- `get_project` — Read — https://policylayer.com/tools/dev-echorelay-management/get-project.md
- `get_receipts` — Read — https://policylayer.com/tools/dev-echorelay-management/get-receipts.md
- …and 47 more: https://policylayer.com/tools/dev-echorelay-management.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=dev-echorelay-management · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-echorelay-management
