AI agents call stellar_transactions to retrieve information from Stellar MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves historical transaction data for a Stellar account. It performs a read-only operation that does not modify, execute, or delete any data. The description explicitly uses 'Get', which is a characteristic read operation. While it returns financial transaction information, it does not move money or create financial obligations, so it does not qualify as Financial.
From the tool's definition Tool name 'stellar_transactions' and description 'Get transaction history for an account' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access stellar_transactions 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 stellar_transactions:
{
"version": "1",
"default": "deny",
"tools": {
"stellar_transactions": {}
}
}stellar_transactions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get transaction history for an account. It is categorised as a Read tool in the Stellar MCP MCP Server, which means it retrieves data without modifying state.
Register the Stellar MCP server in PolicyLayer and add a rule for stellar_transactions: 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.
stellar_transactions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the stellar_transactions 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 stellar_transactions. 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.
stellar_transactions 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.