kyc_start_kyc_inquiry
StartKycInquiry creates a provider inquiry and returns the hosted flow URL. Idempotent within an open inquiry window. Exposed because the Mac app reaches the server only over MCP, and only an inquiry this service opened is one the webhook and GetKycStatus can read.
This record as markdown: /tools/lovieco-lovie-company-formation-mcp-npx/kyc-start-kyc-inquiry.md
What kyc_start_kyc_inquiry does on Lovie Company Formation MCP
AI agents invoke kyc_start_kyc_inquiry to trigger actions in Lovie Company Formation MCP. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
userId | object | Yes | UUID value wrapper. |
templateId | string | — | |
redirectUri | string | — | |
trustedDeviceId | object | — | UUID value wrapper. |
Parameters from the server's own tool schema.
Why kyc_start_kyc_inquiry is rated High
kyc_start_kyc_inquiry 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.
Attacks that exploit this kind of access
The rule that runs kyc_start_kyc_inquiry safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Lovie Company Formation MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For kyc_start_kyc_inquiry, this is the rule to start with:
kyc_start_kyc_inquiry stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Lovie Company Formation MCP, apply this rule, and every kyc_start_kyc_inquiry call is checked against it from then on.
Questions about kyc_start_kyc_inquiry
StartKycInquiry creates a provider inquiry and returns the hosted flow URL. Idempotent within an open inquiry window. Exposed because the Mac app reaches the server only over MCP, and only an inquiry this service opened is one the webhook and GetKycStatus can read. It is categorised as a Execute tool in the Lovie Company Formation MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
kyc_start_kyc_inquiry accepts 4 parameters: userId, templateId, redirectUri, trustedDeviceId. Required: userId. The full parameter table on this page comes from the server's own tool schema.
Register the Lovie Company Formation MCP server in PolicyLayer and add a rule for kyc_start_kyc_inquiry: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Lovie Company Formation MCP. Nothing to install.
kyc_start_kyc_inquiry is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the kyc_start_kyc_inquiry rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for kyc_start_kyc_inquiry. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
kyc_start_kyc_inquiry is provided by the Lovie Company Formation MCP server (lovie). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Lovie Company Formation, and thousands of servers like it.
Across the catalogue