ugf_sol_wait_user_sig_message

WHAT IT DOES

What ugf_sol_wait_user_sig_message does on Universal Gas Framework MCP Server

AI agents invoke ugf_sol_wait_user_sig_message 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 IT NEEDS A POLICY

Why ugf_sol_wait_user_sig_message needs a policy

This tool orchestrates a critical step in a gasless cross-chain transaction: it returns a message for the agent to sign cryptographically and submit. Although the tool itself doesn't execute the signing (the agent does), it is the control point that initiates irreversible blockchain transaction commitment.

From the tool's definition Tool waits for a prepared Solana message and instructs the agent to sign it 'locally with its keypair via nacl.sign.detached', then submit via ugf_sol_submit_user_sig. This is a direct trigger for cryptographic signing and transaction execution on Solana.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ugf_sol_wait_user_sig_message Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ugf_sol_wait_user_sig_message": {
      "limits": [
        {
          "counter": "ugf_sol_wait_user_sig_message_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Universal Gas Framework MCP Server, so you can run agents against it safely.

FAQ

Questions about ugf_sol_wait_user_sig_message

What does the ugf_sol_wait_user_sig_message tool do? +

Wait for the Solana user-sig message UGF prepared. Returns {serialized_message: base64}. Agent signs locally with its keypair via nacl.sign.detached, then calls ugf_sol_submit_user_sig. 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_wait_user_sig_message? +

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

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

Can I rate-limit ugf_sol_wait_user_sig_message? +

Yes. Add a rate_limit block to the ugf_sol_wait_user_sig_message 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_wait_user_sig_message completely? +

Set action: deny in the PolicyLayer policy for ugf_sol_wait_user_sig_message. 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_wait_user_sig_message? +

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