Create a new transaction. Amount in cents (negative = expense, positive = income).
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.
This tool directly creates financial transactions, committing financial operations (expenses or income). Misuse could result in unauthorized financial entries, making it Financial category with critical severity due to direct monetary impact.
From the tool's definition Create a new transaction. Amount in cents (negative = expense, positive = income).
Documented attack patterns abuse exactly the kind of access crow_actual_create_transaction gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for crow_actual_create_transaction:
{
"version": "1",
"default": "deny",
"tools": {
"crow_actual_create_transaction": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to crow_actual_create_transaction is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
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.
Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.