get_transaction
AI agents call get_transaction to retrieve information from ntropy-mcp MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves or queries a transaction record without modifying, deleting, or executing operations. Despite the empty description, the naming convention and server context strongly indicate a read-only retrieval function. Confidence is slightly reduced due to lack of explicit documentation, but the tool name and broader server patterns provide sufficient evidence for Read classification.
From the tool's definition Tool name 'get_transaction' indicates a retrieval operation; no description provided but the pattern aligns with sibling tool 'list_transactions' which is a Read operation. The Ntropy API context suggests querying banking transaction data.
Attacks that exploit this kind of access
get_transaction. It is categorised as a Read tool in the ntropy-mcp MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ntropy-mcp MCP Server MCP server in PolicyLayer and add a rule for get_transaction: 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 ntropy-mcp MCP Server. Nothing to install.
get_transaction 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 get_transaction 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 get_transaction. 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.
get_transaction is provided by the ntropy-mcp MCP Server MCP server (ntropy-network/ntropy-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 →