underwrite
Run the full underwriting: read the token, pay and verify an auditor's seal B, compose and sign seal A around it, publish the body to 0G Storage, and list it on the CollateralRegistry. Refuses with a named code at whichever step fails. Without a key this stops at the quote.
This record as markdown: /tools/0x402-mcp/underwrite.md
What underwrite does on 0x402
AI agents invoke underwrite to trigger actions in 0x402. 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 |
|---|---|---|---|
token | string | Yes | ERC-20 contract address on 0G testnet. |
ltvBps | integer | — | Loan-to-value to list at, in basis points. The auditor's cap always wins. |
settle | boolean | — | Submit the listing transaction. False stops after the seal. |
source | string | — | Local Solidity source for the token, if you have it. Never fetched. |
publish | boolean | — | Upload the seal body to 0G Storage so anyone can fetch it by its hash. |
Parameters from the server's own tool schema.
Why underwrite is rated High
underwrite 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.
Risk signalsHandles credentials or secrets (token)
Attacks that exploit this kind of access
The rule that runs underwrite safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0x402, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For underwrite, this is the rule to start with:
underwrite 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 0x402, apply this rule, and every underwrite call is checked against it from then on.
Questions about underwrite
Run the full underwriting: read the token, pay and verify an auditor's seal B, compose and sign seal A around it, publish the body to 0G Storage, and list it on the CollateralRegistry. Refuses with a named code at whichever step fails. Without a key this stops at the quote. It is categorised as a Execute tool in the 0x402 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
underwrite accepts 5 parameters: token, ltvBps, settle, source, publish. Required: token. The full parameter table on this page comes from the server's own tool schema.
Register the 0x402 MCP server in PolicyLayer and add a rule for underwrite: 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 0x402. Nothing to install.
underwrite 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 underwrite 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 underwrite. 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.
underwrite is provided by the 0x402 MCP server (@0x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 0x402, and thousands of servers like it.
This server
Across the catalogue