MCP (policy generation)

The MCP is the agent-facing surface. Its job is to help an agent author a policy — the guardrail the user will sign — grounded in a real product taxonomy and validated by the same compiler the orchestrator uses to accept it.

Note

Policy generation happens here, on the MCP. Submitting the finished policy and the signed intent happens on the Orchestrator API.

Connecting

The MCP is served over streamable HTTP at the /mcp path of the Delta-hosted MCP endpoint. It’s stateless — point any MCP client at the URL.

Tools

• get_language_guide (no args) — returns the authoring guide: workflow, taxonomy rules, worked examples, and the full policy DSL reference. Call it once before authoring.
• search_taxonomy { query } — semantic search over the product taxonomy. Returns real category paths and the per-category evidence attributes (with the DSL type to declare). Categories must be copied verbatim.
• validate_template { source } — compiles the policy with the real policy compiler. Returns valid + a canonical pretty-print, or a compile error with line:column and an actionable hint.

There is also one resource, guide://policy-authoring, exposing the same content as get_language_guide.

Authoring loop

1. Call get_language_guide once.
2. Call search_taxonomy to ground the policy in real categories + attributes.
3. Draft the policy.
4. Call validate_template; fix and repeat until it compiles.
5. Hand the compiled policy back to the user to sign — registration happens via POST /templates on the orchestrator.