ugf_sol_submit_user_sig

Submit a locally-produced Solana user signature to UGF. Pair with ugf_sol_wait_user_sig_message.

Server Universal Gas Framework MCP Server tychiwallet/ugf-mcp
Category Execute
Risk class High
Parameters 00 required

What ugf_sol_submit_user_sig does on Universal Gas Framework MCP Server

AI agents invoke ugf_sol_submit_user_sig to trigger actions in Universal Gas Framework MCP Server. 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.

Why ugf_sol_submit_user_sig needs a policy

Submitting a user signature to a cross-chain gas framework initiates or authorizes an on-chain transaction. While it is not directly moving money (the financial leg is handled elsewhere), it is an irreversible external operation that triggers blockchain execution. The context of gasless cross-chain transactions means misuse could result in unauthorized transaction authorization.

From the tool's definition 'Submit a locally-produced Solana user signature to UGF' — submits a cryptographic signature that triggers/authorizes a cross-chain transaction on an external system

Questions about ugf_sol_submit_user_sig

What does the ugf_sol_submit_user_sig tool do? +

Submit a locally-produced Solana user signature to UGF. Pair with ugf_sol_wait_user_sig_message. It is categorised as a Execute tool in the Universal Gas Framework MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ugf_sol_submit_user_sig? +

Register the Universal Gas Framework MCP Server MCP server in PolicyLayer and add a rule for ugf_sol_submit_user_sig: 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.

What risk level is ugf_sol_submit_user_sig? +

ugf_sol_submit_user_sig is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit ugf_sol_submit_user_sig? +

Yes. Add a rate_limit block to the ugf_sol_submit_user_sig 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.

How do I block ugf_sol_submit_user_sig completely? +

Set action: deny in the PolicyLayer policy for ugf_sol_submit_user_sig. 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.

What MCP server provides ugf_sol_submit_user_sig? +

ugf_sol_submit_user_sig 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.