Get the transaction receipt by the transaction hash
AI agents call starknet_getTransactionReceipt to retrieve information from Starknet MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves blockchain transaction receipt information based on a provided transaction hash. It is a read-only query operation with no side effects, no data modification, no code execution, and no financial implications. The transaction receipt is already immutable blockchain state that the tool merely queries and returns to the caller.
From the tool's definition Tool name and description indicate it 'Get[s] the transaction receipt by the transaction hash' - a pure query operation that retrieves and returns transaction receipt data without modifying state or triggering external side effects.
Documented attack patterns abuse exactly the kind of access starknet_getTransactionReceipt gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Starknet MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for starknet_getTransactionReceipt:
{
"version": "1",
"default": "deny",
"tools": {
"starknet_getTransactionReceipt": {}
}
} starknet_getTransactionReceipt 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 the transaction receipt by the transaction hash. It is categorised as a Read tool in the Starknet MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Starknet MCP Server MCP server in PolicyLayer and add a rule for starknet_getTransactionReceipt: 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 Starknet MCP Server. Nothing to install.
starknet_getTransactionReceipt 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 starknet_getTransactionReceipt 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 starknet_getTransactionReceipt. 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.
starknet_getTransactionReceipt is provided by the Starknet MCP Server MCP server (milancermak/starknet-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Starknet MCP Server, 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.
21 Starknet MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.