submit_safe_tx_signature

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

Medium RISK CLASS

Category Write

Parameters 43 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/submit-safe-tx-signature.md

WHAT IT DOES

What submit_safe_tx_signature does on VaultPilot MCP

AI agents use submit_safe_tx_signature to create or update resources in VaultPilot MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your VaultPilot MCP environment.

Parameter	Type	Required
`chain`	string	—
`signer`	string	Yes
`safeTxHash`	string	Yes
`safeAddress`	string	Yes

Parameters from the server's own tool schema.

RISK

Why submit_safe_tx_signature is rated Medium

The tool's primary function is to POST/WRITE data (signatures) to Safe Transaction Service, modifying the transaction approval state. While it involves cryptographic operations on financial transactions, it does not directly move funds or create irreversible state changes—it stages transactions for later execution. The actual fund transfer would require separate execution steps.

From the tool's definition Tool submits signatures to Safe Transaction Service via `proposeTransaction` (creates new queue entry) or `confirmTransaction` (adds signature to existing entry). These are write operations that modify transaction queue state on Safe infrastructure.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs submit_safe_tx_signature safely

PolicyLayer is an MCP gateway: it sits between your AI agents and VaultPilot MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For submit_safe_tx_signature, this is the rule to start with:

submit_safe_tx_signature Rate-limited

submit_safe_tx_signature stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "submit_safe_tx_signature": {
      "limits": [
        {
          "counter": "submit_safe_tx_signature_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect VaultPilot MCP, apply this rule, and every submit_safe_tx_signature call is checked against it from then on.

FAQ

Questions about submit_safe_tx_signature

What does the submit_safe_tx_signature tool do? +

After the on-chain approveHash tx has been mined (broadcast via send_transaction from the receipt of prepare_safe_tx_propose or prepare_safe_tx_approve), post the signature to Safe Transaction Service. Verifies on-chain that approvedHashes(signer, safeTxHash) != 0 first — refuses to post when the underlying approval doesn't exist yet. Auto-detects whether to call proposeTransaction (creates a new queue entry — when this server proposed the tx) or confirmTransaction (adds a signature to an existing entry — when another client proposed it). Returns the Safe Web UI deep-link so the user / co-signers can see the queue state. It is categorised as a Write tool in the VaultPilot MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does submit_safe_tx_signature accept? +

submit_safe_tx_signature accepts 4 parameters: chain, signer, safeTxHash, safeAddress. Required: signer, safeTxHash, safeAddress. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on submit_safe_tx_signature? +

Register the VaultPilot MCP server in PolicyLayer and add a rule for submit_safe_tx_signature: 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 VaultPilot MCP. Nothing to install.

What risk level is submit_safe_tx_signature? +

submit_safe_tx_signature is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit submit_safe_tx_signature? +

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

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

submit_safe_tx_signature is provided by the VaultPilot MCP server (vaultpilot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on VaultPilot, and thousands of servers like it.

This server

All 189 VaultPilot tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →