Fetch an array of transactions for a given Stellar address.
AI agents call get-transactions to retrieve information from Josectoscano Stellar without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns transaction history for a Stellar address. It performs a read-only operation that retrieves existing data without modifying, executing code, deleting, or moving funds. The verb 'fetch' confirms passive data retrieval. While the sibling tools create-account, fund-account, and sign-and-submit-transaction perform write/financial/execute operations, this tool does not.
From the tool's definition Tool name 'get-transactions' and description 'Fetch an array of transactions for a given Stellar address' indicate a data retrieval operation with no side effects.
Attacks that exploit this kind of access
Fetch an array of transactions for a given Stellar address. It is categorised as a Read tool in the Josectoscano Stellar MCP Server, which means it retrieves data without modifying state.
Register the Josectoscano Stellar MCP server in PolicyLayer and add a rule for get-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 Josectoscano Stellar. Nothing to install.
get-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 get-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 get-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.
get-transactions 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 →