Check transaction status by hash
AI agents call getTransactionStatus to retrieve information from Plasma Testnet MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries blockchain transaction status by hash, which is a read-only operation with no side effects. It retrieves data about an existing transaction but does not modify, execute, or delete anything. The low severity reflects that misuse would only expose transaction visibility information, not enable harmful actions like fund transfers or smart contract execution.
From the tool's definition Tool name 'getTransactionStatus' and description 'Check transaction status by hash' indicate a query operation that retrieves transaction state information without modifying or executing any operations.
Attacks that exploit this kind of access
Check transaction status by hash. It is categorised as a Read tool in the Plasma Testnet MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Plasma Testnet MCP Server MCP server in PolicyLayer and add a rule for getTransactionStatus: 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 Plasma Testnet MCP Server. Nothing to install.
getTransactionStatus 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 getTransactionStatus 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 getTransactionStatus. 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.
getTransactionStatus is provided by the Plasma Testnet MCP Server MCP server (tairon-ai/plasma-mcp). 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 →