
An enterprise AI agent in production is software that uses a language model to read business inputs, decide the next step and act. It acts in systems such as your ERP, CRM or inbox, every working day. It works under the controls you would give a new employee with system access. The model is the same one you saw in the demo. What makes a production agent different is everything around the model. That covers what the agent may read, which actions it may take, who signs off before money moves, how it is stopped, and who notices when its output drifts.
AI pilots tend to skip those parts because a demo never needs them. AI agents in production need all of them on day one. Each part below uses the same worked example, an invoice that arrives 2.2% over its purchase order.
In December 2025, CISA and the Australian Signals Directorate led the joint guidance Principles for the Secure Integration of Artificial Intelligence in Operational Technology. It defines AI agents as "a type of software that can process data, perform decision-making capabilities, and initiate autonomous actions using AI and ML models." When NIST's Center for AI Standards and Innovation launched its AI Agent Standards Initiative in February 2026, it described agents that "can now work autonomously for hours, write and debug code, manage emails and calendars."
A chatbot that answers a question wrongly produces a bad answer. An agent that acts wrongly posts an invoice, books an appointment or emails a customer. A system of record is where your official data lives, such as your ERP or CRM. Once an agent can write to one, it needs the controls you would put around a new employee with system access. Those checks have to run every time the agent runs.
Take an accounts payable agent. A supplier emails an invoice for €18,400 against a purchase order approved at €18,000. In production, that one run passes five checkpoints before anything reaches the ledger.
If any step fails or times out, the run stops and the invoice lands in the team's manual queue. Our AI invoice automation service is built on this pattern, with a three-way match and an approver for every exception.
A language model is good at reading messy input and writing a clear sentence. It is unreliable at arithmetic and at applying a threshold the same way twice. NIST AI 800-4, Challenges to the Monitoring of Deployed AI Systems (March 2026), puts it plainly: "AI outputs are typically non-deterministic, meaning the AI may exhibit a range of behaviors under the same input conditions." So in a production agent, code produces the numbers and the yes-or-no decisions, and the model writes the words around them.
We built daily MI alerting for IES Limited, a travel insurance group with four brands, on that split. PostgreSQL views calculate every figure, and n8n decides who needs to know. The model receives the finished numbers and writes the narrative. A verification step names any figure the model was not given. A drop in the quote funnel once took IES 20 working days to notice. It now reaches the right Teams channel within 30 minutes of the daily pack landing. Replayed against past data, the system caught all 4 earlier incidents that had a baseline to compare against. IES changed its own alert thresholds 34 times in six weeks without a single developer ticket.
Business rules work the same way. Our post on mapping business rules into the context layer shows how to move discount limits and approval thresholds out of the prompt. They become versioned records, each with an owner.
An agent is only as useful as the systems it can reach. The Model Context Protocol (MCP) gives agents one standard way to call tools and fetch data, instead of a custom connector for each system. Anthropic released it in November 2024. In December 2025, Anthropic contributed it to the Linux Foundation's Agentic AI Foundation. n8n, Zapier and most of the platforms in our AI agent platform comparison support it.
The protocol only carries the requests, so results depend on what flows through it. In a preliminary 2026 student project at NIST's Summer Undergraduate Research Fellowship (SURF), the team put a research database behind an MCP server. It found that "the systemic inclusion of database schemas and handbooks resulted in a statistically significant increase in query success rates." In our builds, describing the data and the rules well has mattered more than which model sits on top. That is the job of an enterprise context layer, and our context layer blueprint covers how to build one.
An agent adds a risk a chatbot does not have: it reads content written by people you do not control. NIST AI 600-1, the Generative AI Profile (July 2024), describes it: "Indirect prompt injection attacks occur when adversaries remotely (i.e., without a direct interface) exploit LLM-integrated applications by injecting prompts into data likely to be retrieved." The same document notes that researchers "have already demonstrated how indirect prompt injections can exploit vulnerabilities by stealing proprietary data or running malicious code remotely on a machine."
For the invoice agent, the attack is a PDF carrying hidden text that tells the agent to change the supplier's bank details. No filter catches every phrasing, so the defence has to be built into how the agent is set up:
If you already run agents on n8n, our n8n consultant service reviews and hardens existing workflows.
Putting a person on every decision sounds safe and fails in practice. NIST AI 800-4 cites Yampolskiy: "one major issue with human-in-the-loop monitoring is that humans may not be able to keep up with the speed and complexity." Reviewers who approve hundreds of routine items a day stop reading them. Ask for approval where the consequence is high, where a rule requires it, or where the agent's confidence is low. Let everything else run.
The stop button matters as much as the approval queue. The CISA-led guidance tells operators to "establish failsafe mechanisms that enable AI systems to fail gracefully without disrupting critical operations" and to make sure processes can "revert to traditional automation or manual" control. NIST AI 600-1 asks for protocols "to ensure GAI systems are able to be deactivated when necessary." In practice, the team needs a manual queue it already knows how to work, and a switch that pauses the agent without a new deployment. Every case the agent declines should produce a report. We built a dental scheduling system for a Dutch Odoo implementation partner, covering 200 practitioners and 1,500 appointments a week. Any appointment its agent cannot place produces a report explaining why, so a planner picks it up with the reason already in hand.
An enterprise AI agent or assistant in production needs monitoring in the six categories NIST AI 800-4 sets out. Functionality asks whether it still works as intended. Operational asks whether it keeps consistent service across its infrastructure. Human factors asks whether it is transparent and its outputs are good. Security asks whether it holds up against attacks and misuse, and compliance asks whether it follows the rules that apply. The sixth category is large-scale impacts. For a working agent, that means tracking sampled accuracy, exception and override rates, and run time and cost per run. It also means tracking approval wait times, blocked tool calls and log completeness. Each one needs an owner and an alert threshold.
Pre-launch testing shows the agent works on the cases you thought of. Monitoring shows what happens on the cases you did not. Our guide to monitoring AI agents in production covers the signals, thresholds and alert routing for each category. The board below shows how they read together.
In the example board, every technical number is healthy. The real problem is in human factors, where an approval has waited three days. The agent is fast, and the process around it is slow. A dashboard of model metrics never shows that kind of issue.
NIST is open about what is still unsolved. The report describes a possible "monitorability tax". That means paying for slightly less capable models or more expensive model runs, so you can still see the model's reasoning. It names a trade-off between privacy and detail, because detailed logs capture personal data. It also notes that the "appropriate metrics to capture is not standardized." Until standards catch up, each agent needs monitors chosen for its own job. Our AI managed services cover that run loop after launch, and enterprise AI governance covers the policy and audit controls around it.
If you are not sure where to start, the AI readiness scorecard takes a few minutes. Our AI Audit ends with a 90-day roadmap of the workflows worth automating first.
An enterprise AI agent is software that uses a language model to read inputs, decide on a next step and take actions. It acts in business systems such as an ERP, CRM or inbox. What makes it enterprise grade is the layer around the model: scoped access, rules that run in code, approvals for high-consequence actions, logging and monitoring.
Give each agent least-privilege credentials, so it can reach only what its job needs. Route every write through a tool gateway with an allow-list. Keep thresholds and calculations in a rules engine or database. Require approval for payments and data changes, and pin the model version. Log every run, and build a manual fallback before launch.
It is an attack that hides instructions in content the agent reads, such as an email, a document or a web page. NIST AI 600-1 describes adversaries who inject prompts "into data likely to be retrieved". The agent may then follow the hidden instructions. The defence is to treat retrieved content as data and to limit what the agent can do. A successful injection then has nothing harmful to trigger.
NIST AI 800-4 groups monitoring into functionality, operational, human factors, security, compliance and large-scale impacts. For a working agent, that means tracking sampled accuracy, exception and override rates, run time and cost, and approval wait times. It also means watching blocked tool calls, log completeness and the downstream effect on the team.
For high-consequence actions, yes. Reviewing every routine decision tends to fail, because reviewers cannot keep up and start approving without reading. Route the decisions that carry risk to a named approver and let the rest run under monitoring.
Put your first agent into production
In a 30-minute discovery call, you speak directly with an AI engineer about the workflow you want to automate. You also cover the systems it touches and the controls it needs. If an audit is the right first step, we will tell you and scope it on the call.