Submit proof of a locally-broadcast vault payment tx. Pair with ugf_vault_build_tx.
AI agents use ugf_vault_submit_signed to commit financial operations through Universal Gas Framework MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool submits a vault payment transaction as part of a cross-chain gasless transaction framework. It is directly involved in committing a financial operation (payment) on-chain. Even though it submits 'proof' of an already-broadcast transaction, it finalizes or triggers the cross-chain financial flow.
From the tool's definition Submit proof of a locally-broadcast vault payment tx
Attacks that exploit this kind of access
Submit proof of a locally-broadcast vault payment tx. Pair with ugf_vault_build_tx. It is categorised as a Financial tool in the Universal Gas Framework MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Universal Gas Framework MCP Server MCP server in PolicyLayer and add a rule for ugf_vault_submit_signed: 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 Universal Gas Framework MCP Server. Nothing to install.
ugf_vault_submit_signed is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the ugf_vault_submit_signed 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 ugf_vault_submit_signed. 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.
ugf_vault_submit_signed is provided by the Universal Gas Framework MCP Server MCP server (tychiwallet/ugf-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →