Freeze an MCP tool into a skill
Turns one equipped MCP tool (see the tools list) into a frozen mcp skill on the agent. The agent never freeforms the call: only the parameters you expose become the skill’s inputs, and pinned arguments are fixed at runtime. Every required input must be pinned or exposed, and sensitive fields (government ID, financial, credential, health) can’t be pinned or exposed. Because an MCP tool carries no read/write metadata, the skill is treated as a write (needs confirmation, runs non-parallel) unless you attest that it’s read-only. allowedFields is deny-by-default — list the dotted field paths the agent is allowed to receive back.
Authorizations
Flowyte secret API key (Authorization: Bearer flowyte_sk_live_…). Scope-gated; is scoped to your organization — a key can never reach another tenant. The listed scopes in each operation's apiKey requirement are the scopes that key must hold. The tokenUrl is nominal: keys are minted in the dashboard.
Path Parameters
google_calendar, google_sheets, calendly, hubspot, square, opentable, shopify, postgres, mysql, zapier Body
The equipped MCP tool to freeze to (stamped into execution_config.tool_name).
The LLM-facing skill/function name.
The LLM-facing skill description.
Operator-pinned args (override/augment LLM args); the second lock. Cannot overlap exposedParams; sensitive-PII fields are refused.
The subset of the tool's input the LLM may fill → becomes parameters_schema (byte-faithful sub-schemas). Sensitive-PII fields are refused.
Dotted leaf paths (from a probe) the agent may READ back. Deny-by-default: an empty list returns NO data (a warning is emitted).
Optional per-call overall timeout (bounded at 25s; the mcp type is slow-listed so filler masks the dip).
Start enabled (default true; the confirm gate — not a draft flag — protects a write).
When attestedRead is true, DOWNGRADES the fail-closed write to an un-gated read, recorded verbatim (who + when + note).
Optional AGENTIC block — present to freeze ONE concrete action from a Zapier AGENTIC (dynamic-discovery) server (see POST …/tools/{tool}/resolve). When present, the server RE-RESOLVES the action from selectedApi + action + parentParams (never trusting a client-supplied schema), synthesizes a CLOSED schema, and rejoins the same freeze pipeline. instructions/output are OPERATOR-authored and LOCKED — they are stored, NEVER LLM-filled, and are NOT schema inputs (listing them in exposedParams is rejected). Omit for the classic per-tool freeze (unchanged).
Response
The created (frozen) mcp skill, plus authoring warnings and whether it was attested a read.