formation_get_domain_auth_code
Reveals the domain's transfer authorization (EPP) code and lifts the transfer lock — the customer's exit door, shown once and never stored. Requires a trusted-device approval: open one with identity's create-approval-session tool (action_type domain_auth_code_reveal, payload {domain}), have the u...
This record as markdown: /tools/lovieco-lovie-company-formation-mcp-npx/formation-get-domain-auth-code.md
What formation_get_domain_auth_code does on Lovie Company Formation MCP
AI agents call formation_get_domain_auth_code to retrieve information from Lovie Company Formation MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | — | |
companyId | object | Yes | UUID value wrapper. |
approvalSessionId | object | — | UUID value wrapper. |
Parameters from the server's own tool schema.
Why formation_get_domain_auth_code is rated Low
Even though formation_get_domain_auth_code only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs formation_get_domain_auth_code 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 formation_get_domain_auth_code, this is the rule to start with:
formation_get_domain_auth_code is read-only, so it stays allowed. 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 formation_get_domain_auth_code call is checked against it from then on.
Questions about formation_get_domain_auth_code
Reveals the domain's transfer authorization (EPP) code and lifts the transfer lock — the customer's exit door, shown once and never stored. Requires a trusted-device approval: open one with identity's create-approval-session tool (action_type domain_auth_code_reveal, payload {domain}), have the user approve on their phone, then pass the session id as approval_session_id. It is categorised as a Read tool in the Lovie Company Formation MCP MCP Server, which means it retrieves data without modifying state.
formation_get_domain_auth_code accepts 3 parameters: domain, companyId, approvalSessionId. Required: companyId. 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 formation_get_domain_auth_code: 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.
formation_get_domain_auth_code is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the formation_get_domain_auth_code 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 formation_get_domain_auth_code. 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.
formation_get_domain_auth_code 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.
This server
Across the catalogue