evaluate_transaction
Alias for evaluateTransaction: Executes full multi-factor TBML evaluation pipeline.
This record as markdown: /tools/nitrostack/evaluate-transaction.md
What evaluate_transaction does on Nitrostack
AI agents invoke evaluate_transaction to trigger actions in Nitrostack. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why evaluate_transaction is rated High
Runs a full evaluation pipeline, triggering complex multi-factor processing with broad potential effects.
From the tool's definition Executes full multi-factor TBML evaluation pipeline
Attacks that exploit this kind of access
The rule that runs evaluate_transaction 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 evaluate_transaction, this is the rule to start with:
evaluate_transaction stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 evaluate_transaction call is checked against it from then on.
Questions about evaluate_transaction
Alias for evaluateTransaction: Executes full multi-factor TBML evaluation pipeline. It is categorised as a Execute tool in the Nitrostack MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nitrostack MCP server in PolicyLayer and add a rule for evaluate_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 Nitrostack. Nothing to install.
evaluate_transaction is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the evaluate_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 evaluate_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.
evaluate_transaction 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.
Across the catalogue