crow_actual_create_transaction
Create a new transaction. Amount in cents (negative = expense, positive = income).
This record as markdown: /tools/kh0pper-crow/crow-actual-create-transaction.md
What crow_actual_create_transaction does on Crow
AI agents use crow_actual_create_transaction to commit financial operations through Crow, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why crow_actual_create_transaction is rated Critical
This tool creates financial transactions, directly committing financial obligations or recording monetary movements. Misuse could result in fraudulent or erroneous financial records, making it Financial category with critical severity.
From the tool's definition "Create a new transaction. Amount in cents (negative = expense, positive = income)."
Attacks that exploit this kind of access
The rule that runs crow_actual_create_transaction safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crow_actual_create_transaction, this is the rule to start with:
Any call to crow_actual_create_transaction is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every crow_actual_create_transaction call is checked against it from then on.
Questions about crow_actual_create_transaction
Create a new transaction. Amount in cents (negative = expense, positive = income). It is categorised as a Financial tool in the Crow MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Crow MCP server in PolicyLayer and add a rule for crow_actual_create_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 Crow. Nothing to install.
crow_actual_create_transaction is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the crow_actual_create_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 crow_actual_create_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.
crow_actual_create_transaction is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
Across the catalogue