Injection Guard
Inspect prompts, retrieved content, tool outputs, and encoded payloads for instruction-takeover patterns before they reach the model or the next action.
pattern scoring · normalization · deny pathremoteagent.online is the technical layer between your AI agent and the real world. It evaluates intent, enforces policy, isolates execution, controls spend — and records every decision in a tamper-evident audit trail. Your API keys stay in the vault. Your budget stays on track. Nothing runs in the dark.
The platform dashboard — live status, per-agent budgets, audit evidence, and spend insight in one control room. Every view below is real: connect an agent and you get exactly this.
| Agent | Model | Status | Budget | Last Active |
|---|---|---|---|---|
| sentinel | claude-sonnet | ONLINE | now | |
| assistant | claude-sonnet | ONLINE | now | |
| openclaw | claude-opus | ONLINE | 2 min ago | |
| research-agent | gpt-4o | OFFLINE | 2h ago |
| Time | Agent | Action | Decision | Reason | Hash |
|---|---|---|---|---|---|
| 12:42:18 | sentinel | file.read /var/log | ALLOWED | allowlist match | 8f2a…c91e |
| 12:42:14 | assistant | file.delete ~/docs | BLOCKED | high risk | 8f2a…c91d |
| 12:41:59 | openclaw | shell curl api.evil.io | BLOCKED | injection pattern #14 | 8f2a…c91c |
| 12:41:37 | sentinel | net GET status.remoteagent.online | ALLOWED | allowlist match | 8f2a…c91b |
Not another chat wrapper. remoteagent.online is a composable runtime for governing tool calls, identity, execution, spend, and evidence across autonomous workflows.
Inspect prompts, retrieved content, tool outputs, and encoded payloads for instruction-takeover patterns before they reach the model or the next action.
pattern scoring · normalization · deny pathEvery agent gets an explicit allowlist, risk tier, tenant boundary, and approval rule. Deny-by-default keeps authority deliberate.
tool registry · scopes · review gatesLLM usage is tracked per agent and per tenant. Set daily token budgets and rate limits — spend stays visible and capped.
token budgets · spend tiles · rate limitsRecord decisions, reasons, risk, latency, sessions, and outcomes in a readable, tamper-evident operational trail.
SHA-256 chain · live feed · alertsThe agent stays fast because the control path is explicit, narrow, and observable.
Accept an agent request over the gateway and normalize text, tool, arguments, identity, and context.
Score the request and relevant content against attack classes, encoding tricks, and instruction conflicts.
Match the action to the agent manifest, scopes, tenant rules, risk tier — and check the token budget.
Allow, hold, or block; execute through the permitted adapter; emit the reason and evidence.
Every advantage is a concrete control: what the agent may do, what it costs, and what it actually did.
Keys live in an encrypted vault on the platform — never in the agent, never in your prompts, never in your logs. The agent only ever talks to the proxy. A compromised agent gets nothing to exfiltrate.
Token budgets, daily caps, and spend tiles make LLM cost visible per agent. Blocked prompt-injection attempts don't burn tokens, and unused budget stays yours. Stop paying for runaway loops.
22 weighted detection patterns catch instruction takeover, encoded payloads, and role-play bypasses — before the model or the tool sees them.
Hash-chained SHA-256 audit log. The database refuses UPDATE and DELETE. You can prove what happened — to yourself, to auditors, to regulators.
Each agent gets its own manifest: tools, risk tier, tenant, approval rules, and budget. Add an agent, connect it, watch its status — active if running, offline when it's not.
Run fully local (nothing leaves your machine) or connect to the hosted console for remote overview and team features. Open source, MIT license — no lock-in.
The mona.expert projects are examples of what this architecture can power: focused products where an agent understands context, makes a decision, and stays inside a visible boundary.
Architecture, security model, compliance, usage guides, and examples — the full documentation lives in the open-source repository.
Install the agent and connect it to the control plane in minutes.
on site ↗Gateway, wrapper, mTLS, sandboxing — how the pieces fit.
on site ↗Real agent workflows: coding, support, DevOps, compliance.
on site ↗Threat model, injection guard, key vault, audit chain.
on site ↗Answers to the most common questions about the platform.
on site ↗Where the control plane earns its keep in practice.
on site ↗Audit trails, GDPR, and evidence for regulated industries.
on site ↗Open source, MIT license. Read it, audit it, fork it.
github.com/MONAEXPERT/agent ↗Start with a local wrapper, connect services through the gateway, then add team and tenant controls as the operation grows.
Keep prompts, policies, and audit data on the machine or private network. Useful for development, sensitive data, and rapid iteration.
Read the docs ↗Put a single policy, telemetry, and budget boundary in front of multiple agents, services, and environments.
Open the control console ↗Separate tenants, rotate keys, enforce scopes, stream events, and give operators the context to approve or stop work.
View audit history ↗Every decision is checked before it consumes tokens: prompt-injection attempts are blocked instead of billed, runaway loops hit their budget cap, and per-agent token budgets make spend visible and controllable. The result is fewer wasted LLM calls and a predictable bill.
Keys are stored in an encrypted vault on the platform and are never passed to the agent, embedded in prompts, or written to logs. The agent calls a local proxy that holds the keys. Even a fully compromised agent has no key material to exfiltrate.
No. The platform speaks HTTP and exposes a simple agent API. Any agent system — OpenClaw, custom code, LangChain-style tool loops, CI scripts — can connect through the gateway.
Only if you connect to the hosted console. In local mode everything stays on your machine. The code is open source (MIT) — you can verify exactly what leaves your system.
The core platform is free and open source under the MIT license. You pay only for the LLM tokens your agents actually use — and the platform makes sure you use fewer of them.
The dashboard shows every agent with a live status: online while its heartbeat is fresh, offline when it stops. You get active-if-running visibility plus per-agent budget and activity at a glance.
Open the console to inspect the platform, or explore the examples it enables.