AI agents call tx_info to retrieve information from Crypto Multi-MCP Hub without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
In the context of a crypto command center, 'tx_info' most likely retrieves transaction details from the blockchain—a read-only operation with no side effects. The empty description introduces some uncertainty, but the tool name and server context (market data, on-chain data) suggest data retrieval rather than execution, modification, or deletion.
From the tool's definition Tool name 'tx_info' suggests transaction information retrieval. The description is empty, but the naming pattern aligns with query/fetch operations common in blockchain explorers and crypto APIs (e.g., 'get_tx_info', 'fetch_transaction').
Documented attack patterns abuse exactly the kind of access tx_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crypto Multi-MCP Hub, and nothing reaches the server without passing your rules. This is the rule we recommend for tx_info:
{
"version": "1",
"default": "deny",
"tools": {
"tx_info": {}
}
}tx_info 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.
tx_info. It is categorised as a Read tool in the Crypto Multi-MCP Hub MCP Server, which means it retrieves data without modifying state.
Register the Crypto Multi-MCP Hub MCP server in PolicyLayer and add a rule for tx_info: 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 Crypto Multi-MCP Hub. Nothing to install.
tx_info 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 tx_info 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 tx_info. 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.
tx_info is provided by the Crypto Multi-MCP Hub MCP server (pellenybe/crypto-mcp-server---by-corax-colab). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Crypto Multi-MCP Hub, 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.
48 Crypto Multi-MCP Hub tools catalogued and risk-classified — across an index of 43,000+ MCP servers.