get_recent_transactions
Get the most recent transactions, sorted newest first.
This record as markdown: /tools/nitrostack/get-recent-transactions.md
What get_recent_transactions does on Nitrostack
AI agents call get_recent_transactions to retrieve information from Nitrostack without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_recent_transactions is rated Low
Retrieves transaction data without modification, creation, or deletion capabilities.
From the tool's definition Get the most recent transactions, sorted newest first.
Attacks that exploit this kind of access
The rule that runs get_recent_transactions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nitrostack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_recent_transactions, this is the rule to start with:
get_recent_transactions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nitrostack, apply this rule, and every get_recent_transactions call is checked against it from then on.
Questions about get_recent_transactions
Get the most recent transactions, sorted newest first. It is categorised as a Read tool in the Nitrostack MCP Server, which means it retrieves data without modifying state.
Register the Nitrostack MCP server in PolicyLayer and add a rule for get_recent_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 Nitrostack. Nothing to install.
get_recent_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 get_recent_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 get_recent_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.
get_recent_transactions is provided by the Nitrostack MCP server (nitrocloudofficial/nitrostack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nitrostack, and thousands of servers like it.
This server
Across the catalogue