list_transactions
AI agents call list_transactions 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.
List and get operations retrieve data without side effects. Even though the description is empty (lowering confidence slightly), the tool name 'list_transactions' clearly indicates iteration/retrieval of transaction records from the Ntropy banking API, consistent with Read category operations. No destructive, financial, or executable operations are suggested.
From the tool's definition Tool name 'list_transactions' indicates data retrieval. Description is empty, but the naming convention and the context of sibling tools (enrich_transaction, get_transaction, get_account_holder) consistently show Read-pattern tools using 'get', 'list', and…
Attacks that exploit this kind of access
list_transactions. 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 list_transactions: 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.
list_transactions 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 list_transactions 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 list_transactions. 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.
list_transactions 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 →