Sign and submit a Soroban transaction to the Stellar network.
AI agents use sign-and-submit-transaction to commit financial operations through Josectoscano Stellar — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool signs and submits transactions to the Stellar blockchain network. Stellar is a financial protocol for transferring value (payments, asset exchanges, etc.). Submitting a signed transaction is an irreversible financial operation that can move funds, create trustlines, or execute smart contracts on the network. The sibling tools (create-account, fund-account) further confirm this is a financial context.
From the tool's definition Sign and submit a Soroban transaction to the Stellar network
Attacks that exploit this kind of access
Sign and submit a Soroban transaction to the Stellar network. It is categorised as a Financial tool in the Josectoscano Stellar MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Josectoscano Stellar MCP server in PolicyLayer and add a rule for sign-and-submit-transaction: 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 Josectoscano Stellar. Nothing to install.
sign-and-submit-transaction 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 sign-and-submit-transaction 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 sign-and-submit-transaction. 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.
sign-and-submit-transaction is provided by the Josectoscano Stellar MCP server (@iflow-mcp/josectoscano-stellar-mcp-server). 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 →