The MCP simulate_call tool description does not warn that state-changing calls may have side effects if the RPC simulate endpoint changes behavior

[Lost-Z]

Summary

The simulate_call tool description in crates/lumenqraph-mcp/src/tools.rs says the call is a dry-run and nothing is signed or broadcast. This is correct for the current Soroban RPC implementation. However, if an AI agent calls simulate_call with a state-changing function and the RPC endpoint's behavior changes (e.g. a future Soroban upgrade makes simulation have on-chain effects), the agent has no way to detect this. The warning in the tool description is the only safeguard.

Expected Behavior

The tool description should be explicit about the trust boundary: Lumenqraph itself does not submit transactions, but the safety guarantee ultimately depends on the RPC endpoint's simulation semantics.

Proposed Solution

• Update the simulate_call tool description to explicitly state the trust boundary: This relies on the Soroban RPC's simulateTransaction endpoint returning without submitting to the network. Lumenqraph does not sign or broadcast anything.
• Add the same note to the /simulate endpoint documentation in docs/API.md

Affected Files

• crates/lumenqraph-mcp/src/tools.rs
• docs/API.md

[Obaara293]

@Obaara293 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi maintainer, I've reviewed the issue and I've recognized the solution, kindly assign this to me to get the best result.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Obaara293 to this issue.

[devNuel]

@devNuel has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello, I’ve carefully reviewed the issue description and have a clear understanding of the expected outcome. I’d be delighted to take this on and contribute to resolving it effectively.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @devNuel to this issue.

[Toyosi5566]

@Toyosi5566 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I can update the trust boundary caveat in crates/lumenqraph-mcp/src/tools.rs and mirror it in docs/API.md to explicitly ground safety on Soroban RPC's simulation semantics please assign this to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Toyosi5566 to this issue.

[Aswumi]

@Aswumi has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi maintainer I would love to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Aswumi to this issue.

[Demilade10]

@Demilade10 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi I can fix this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Demilade10 to this issue.

[williamsokperez-arch]

@williamsokperez-arch has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

id love to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @williamsokperez-arch to this issue.

[drips-wave]

Congratulations, @williamsokperez-arch! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @williamsokperez-arch: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @williamsokperez-arch as part of the Stellar Wave Program's 8th Wave 🥳

😎 @williamsokperez-arch: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.