AI agents invoke soroban_build_and_optimize to trigger actions in Stellar MCP. 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.
This tool executes a build process that compiles and optimizes smart contract code. While building itself doesn't directly modify blockchain state (unlike the sibling payment/asset tools), it does trigger execution of external build tools and compilation logic whose effects depend on the contract code provided as arguments. This is fundamentally an Execute operation rather than a simple Read operation.
From the tool's definition Tool name explicitly states 'build_and_optimize' and description says 'Build and optimize a Soroban contract'.
Documented attack patterns abuse exactly the kind of access soroban_build_and_optimize gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Stellar MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for soroban_build_and_optimize:
{
"version": "1",
"default": "deny",
"tools": {
"soroban_build_and_optimize": {
"limits": [
{
"counter": "soroban_build_and_optimize_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} soroban_build_and_optimize 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.
Free to start. No card required.
Build and optimize a Soroban contract. It is categorised as a Execute tool in the Stellar MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Stellar MCP server in PolicyLayer and add a rule for soroban_build_and_optimize: 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 Stellar MCP. Nothing to install.
soroban_build_and_optimize is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the soroban_build_and_optimize 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 soroban_build_and_optimize. 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.
soroban_build_and_optimize is provided by the Stellar MCP server (syronlabs/stellar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Stellar MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 Stellar MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.