Low Risk

getTransaction

Used to look up transaction by signature (64 byte base58 encoded string)

How to control getTransaction ↓

AI agents call getTransaction to retrieve information from Solana Model Context Protocol (MCP) Demo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves transaction information from the Solana blockchain by signature lookup. It performs a read-only query operation with no side effects, no data modification, no code execution, and no financial impact. The low severity reflects minimal blast radius - an AI agent misusing this would only retrieve existing public blockchain data.

From the tool's definition Tool description explicitly states it is 'Used to look up transaction by signature' - a pure query operation that retrieves transaction data without modification or execution.

Documented attack patterns abuse exactly the kind of access getTransaction gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Solana Model Context Protocol (MCP) Demo, and nothing reaches the server without passing your rules. This is the rule we recommend for getTransaction:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "getTransaction": {}
  }
}

getTransaction is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Solana Model Context Protocol (MCP) Demo — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the getTransaction tool do? +

Used to look up transaction by signature (64 byte base58 encoded string). It is categorised as a Read tool in the Solana Model Context Protocol (MCP) Demo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getTransaction? +

Register the Solana Model Context Protocol (MCP) Demo 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 Solana Model Context Protocol (MCP) Demo. Nothing to install.

What risk level is getTransaction? +

getTransaction is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit getTransaction? +

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.

How do I block getTransaction completely? +

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.

What MCP server provides getTransaction? +

getTransaction is provided by the Solana Model Context Protocol (MCP) Demo MCP server (solana-foundation/solana-dev-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Solana Model Context Protocol (MCP) Demo tool call.

Deterministic rules across all 4 Solana Model Context Protocol (MCP) Demo tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4 Solana Model Context Protocol (MCP) Demo tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.