RiskMandate v1.38.0
Rule RM-R0010 · v1.0.0 · ask me first

Do you want your agent to spend money on an account it holds?

It solves the problem by creating a bigger machine, calling a paid API in a loop, or running a job that is billed by the hour. The bill arrives at the end of the month.

What you get: You see the cost before anything that costs money starts.

The capability: Spend money or tokens against an account it holds (write.budget.tenant). Undo: cannot be undone.

All rules: the index · This page as markdown: spend-money.md

01 · The line

Paste this into your agent's instructions, and it should ask you first.

For Claude Code, that is CLAUDE.md in the project or in your home directory; for Claude on the web or the desktop, a project's instructions or your personal preferences. The one line is enough to try it; the paragraph tells the agent why, and what counts.

The one line
Before anything that costs money (creating cloud resources, calling paid APIs repeatedly, buying anything), tell me what it will cost and wait for a yes.
The paragraph
Spending money is mine to decide. Before creating or resizing cloud resources, starting anything billed by time or by use, calling a paid API more than a handful of times, or buying anything, tell me what it is, roughly what it will cost, and how to stop it, and wait for a yes.
02 · What that line is

A request to the agent, not a control.

In the vocabulary every published behaviour policy uses, a line in the agent's instructions is an expectation: a rule in prose, enforced by nobody. A rule in prose is inside the boundary the agent operates in. All four major model providers stated in their own 2026 words that an instruction at this layer can be bypassed. It changes what the agent usually does, which is worth having; it does not hold when the agent is talked out of it, confused, or reading somebody else's instructions in a web page.

We have not found a stronger barrier for this one in the vendor's documentation. If you know of one, tell us below.

03 · Where your agent already has it

This is a row in 2 published behaviour policies, with what stands in the way today.

Read from each vault's own grant, as published. The barrier is what was found in that deployment, before any rule.

AgentBarrierWhat the behaviour policy says
A scheduled jobnoneif the credential is billed
n8n, owner API keynonea real model credential was added by the deployer through the UI and a real execution returned a model response through the node — spend against that account, as the workflow's author. The first attempt failed with "does not have access to the credential": a wrong reference from ambiguous name matching between two credentials of the same type, not a barrier, found only once the MCP interface could list them.
04 · Before and after

Not run yet. It will be, on our own deployment.

Every rule gets one run without the line and one with it, on a deployment we are entitled to run, dated, stopped before anything irreversible. How these are run.

05 · Did it work for you?

Tell us, and the rule gets better.

Each link opens the contact form with this rule's id and version filled in. It is encrypted in your browser and read by a person. Nothing is sent until you press send.

06 · One row, and the whole agent

A rule is one row. The ABP is every row, for your agent.

If this one made sense, the Agent Behaviour Policy is the same idea for everything your agent can reach: what it can do, what you authorised, the gap, and what stands in the way of each thing.

Versions

  • v1.0.0 · 8 October 2026 · First version, written from the published rows with nothing in the way.