01 / Code
Code-first developer
Validate contracts, policy and the isolated reference runtime.
Open code quickstart →PALO-AI quickstarts
Start with one isolated, reversible action. Prove the governed path and its evidence before expanding tools, credentials or authority.
Select by build mode
01 / Code
Validate contracts, policy and the isolated reference runtime.
Open code quickstart →02 / Visual
Install package 0.2 on a disposable self-hosted canvas and import the safe demo.
Open n8n quickstart →03 / Rapid
Expose only a narrow, authenticated preview toolset to the agent.
Open MCP quickstart →01 / Code-first
Prerequisites: Node.js/npm, a local checkout and a supported shell.
Schemas, Rego tests and the reference agentic validation suite pass in your checkout.
What it does not proveProduction workload identity, connector isolation, HA, KMS custody or independent assurance.
npm ci
npm run opa:install
npm run validate:agentic
Expected result: schema, registry, policy and full-cycle reference checks complete without failures.
02 / n8n and visual builders
Prerequisites: a disposable self-hosted n8n instance, Docker or an isolated host, and no production credentials.
The package builds, verifies and can represent the governed decision and full-cycle action paths.
What it does not proven8n verification, npm provenance, a production connector or unavoidable interception of alternate credentials.
cd packages/n8n-nodes-palo-ai && npm ci &&
npm run verify && npm pack
Install it only in your disposable self-hosted environment, then restart n8n.
For the local Docker demo use gateway
http://host.docker.internal:8787 and the
repository’s explicitly demo-only token.
examples/n8n-demo/PALO-AI-full-cycle-assurance-demo.json
PALO Governance is an advisory decision gate. PALO Governed Action represents the protected execution and verification path. Direct equivalent credentials remain a bypass and must be removed for real enforcement.
Expected result: visible Verified, Review Required, Denied and Execution Failed routes using synthetic data.
03 / Copilot Studio and MCP
Prerequisites: an isolated PALO remote MCP preview, HTTPS, a preview credential and permission to configure tools in Copilot Studio.
Copilot Studio can discover and call selected PALO MCP tools over authenticated Streamable HTTP.
What it does not proveUniversal interception, OAuth/OIDC production identity or removal of direct equivalent actions.
Define its resource, allowed operation, accountable reviewer and expected effect.
Use the server tool allowlist; do not publish the entire governance surface to the agent.
The current reference remote transport supports a shared API-key/bearer preview boundary. OAuth/OIDC workload identity is the recommended production design and remains a readiness gate.
Follow Microsoft’s Streamable HTTP MCP onboarding flow, then inspect every imported tool.
If the agent can still call the operational system directly, PALO is advisory rather than an enforcement boundary.
Expected result: the agent sees only selected governance tools and evaluation remains inside a declared preview boundary.
Choose deliberately
| Route | First proof | Main bypass to remove | Next destination |
|---|---|---|---|
| Code-first | Contracts and reference tests pass | Direct SDK/tool credential | Eight-step wizard |
| n8n | Four full-cycle branches are visible | Alternate credential or direct node | Hands-on assurance guide |
| Copilot / MCP | Narrow tool discovery and call | Direct equivalent agent action | Integration guide |