BetaApp monitoring watches a running application's log files, HTTP traffic and LLM features, around the clock, and flags attacks such as injection, path traversal, reverse shells, prompt injection, attempts to extract API keys and credentials written to logs. It runs as the open-source beam CLI next to your app, or inside a Node.js or Next.js app with its SDK. It never blocks requests or changes the app, and it's built to stay out of the way: a hard CPU cap, flat memory, and no effect on your app when AgentBeam is down. Detection is heuristic, so findings are leads to review, not verdicts.
The same CLI checks your lockfiles against AgentBeam's CVE database, so one token covers both live traffic and the dependencies you ship.
beam monitor tails log files and HTTP access logs, or piped output with --stdin, and matches lines against attack patterns. Repeats are folded per window, grouped by client IP for traffic, and floods are summarised.
Injection
Payloads in query strings, bodies and logged parameters, including JNDI strings of the Log4Shell kind.
Traversal
Requests reaching for ../ sequences, .env files, SSH keys and other files that should never be served.
Payloads
Serialized-object payloads, prototype pollution attempts and cross-site scripting markers.
Execution
Commands that fetch and run remote code, open reverse shells or hide the command in an encoding.
Cloud
Parameters that point the server at itself, its network or an instance metadata endpoint, and schemes like gopher:// that only an attacker wants fetched.
AI
Prompt injection (including text hidden in invisible Unicode or base64), forged chat markers, jailbreaks, system prompt extraction, attempts to get the app's API keys, exfiltration links in model output, and one client flooding your LLM endpoints.
Leaks
LLM and cloud keys written to logs or model output, and a .env or .git/config file actually served. Attack-tool user agents and repeated failed sign-ins are flagged too.
01
An owner or admin turns on App monitoring, adds each app (for example "bgremover") and copies its BEAM_APP_TOKEN. The token is shown once.
02
Point it at log files, pipe output in with --stdin, or add the SDK to a Node.js app. beam monitor test sends one test finding end to end, and beam monitor configure saves the setup so the service runs with no flags.
03
Findings are filtered per app. Webhooks post to Slack or Discord natively, or send signed JSON, each with its own minimum severity and optional app filter.
App monitoring needs an AgentBeam workspace with it turned on by an owner or admin. Usage counts toward a monthly allowance that depends on your plan.
No. It only watches. It never blocks requests, changes your app or sits in the request path, so it cannot take your service down. It tells you an attack pattern appeared; stopping it is up to your own controls.
No. Raw log lines stay on the server. Only redacted findings are sent: the rule, severity, file, a count and a redacted excerpt of at most 600 characters.
It is heuristic. Pattern matching will flag some harmless lines and miss some real attacks. Strict level surfaces more, Light only critical findings, and the optional LLM second opinion helps triage flagged lines.
Yes. beam monitor --llm openai (or anthropic, gemini, groq, openrouter, mistral and others) uses the key already in that server's environment, and the SDK does the same with createAppMonitor({ llm: "openai" }). The key goes only to that provider; AgentBeam receives the verdict, never the key.
Nothing. Reports are sent in the background with a 5-second timeout and back off while AgentBeam is unreachable; requests never wait on it. Detection has a hard CPU cap and bounded memory either way.
beam cve check . reads lockfiles for npm, yarn, pnpm, bun, pip, poetry, uv, Go, Cargo, composer, Bundler, NuGet, Gradle, mix, Swift Package.resolved and GitHub Actions workflows. It sends only package names and versions, and exits 2 when a finding meets --fail-on. In CI it authenticates with BEAM_APP_TOKEN.
Yes. Install the bundled skills with npx @agent-beam/beam add skill agentbeam-setup -g --all-agents, and likewise agentbeam-app-monitoring. Beam scans a skill before installing it.
Add an app, run beam monitor beside it, and get redacted findings in Slack, Discord or your own webhook. It works whether or not you already have an AgentBeam account.