Retrieves details about a transaction, including sender, recipient, value, status, and deployed contract address if applicable.
AI agents call getTransactionInfo to retrieve information from Token Minter without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs only information retrieval with no side effects. It queries transaction data on the blockchain but does not execute code, modify state, delete data, or move funds. The blast radius of misuse is minimal—an attacker could only gain visibility into transaction history, not alter it or trigger actions.
From the tool's definition Tool name 'getTransactionInfo' and description 'Retrieves details about a transaction' indicate a query operation that fetches and returns transaction metadata (sender, recipient, value, status, contract address) without modifying state.
Documented attack patterns abuse exactly the kind of access getTransactionInfo gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Token Minter, and nothing reaches the server without passing your rules. This is the rule we recommend for getTransactionInfo:
{
"version": "1",
"default": "deny",
"tools": {
"getTransactionInfo": {}
}
}getTransactionInfo 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.
Retrieves details about a transaction, including sender, recipient, value, status, and deployed contract address if applicable. It is categorised as a Read tool in the Token Minter MCP Server, which means it retrieves data without modifying state.
Register the Token Minter MCP server in PolicyLayer and add a rule for getTransactionInfo: 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 Token Minter. Nothing to install.
getTransactionInfo 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 getTransactionInfo 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 getTransactionInfo. 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.
getTransactionInfo is provided by the Token Minter MCP server (kukapay/token-minter-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Token Minter, 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.
6 Token Minter tools catalogued and risk-classified — across an index of 43,000+ MCP servers.