Used to look up transaction by signature (64 byte base58 encoded string)
AI agents call getTransaction to retrieve information from AMOCA Solana MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
getTransaction is a read-only operation that queries Solana blockchain data. It takes a transaction signature as input and returns transaction details without creating, modifying, deleting, or executing any operations. This is a standard informational lookup with no blast radius for misuse.
From the tool's definition Tool description states 'look up transaction by signature' - a query operation that retrieves blockchain transaction data with no modifications or side effects.
Attacks that exploit this kind of access
Used to look up transaction by signature (64 byte base58 encoded string). It is categorised as a Read tool in the AMOCA Solana MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AMOCA Solana MCP Server MCP server in PolicyLayer and add a rule for getTransaction: 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 AMOCA Solana MCP Server. Nothing to install.
getTransaction 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 getTransaction 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 getTransaction. 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.
getTransaction is provided by the AMOCA Solana MCP Server MCP server (manolaz/amoca-solana-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 →