Security and trust

What the laptop command reads and sends

It opens the MCP config files of Claude Code, Claude Desktop, Cursor, VS Code and Windsurf, and the Claude Code skill folders. It only reads them. It never runs, installs or imports any of the AI tools it finds.

It sends a list of the MCP servers and skills on the computer. For each server, that is its name in the config, its package and plain version, and the program that starts it, such as npx. For a remote server it is the host, and for a skill it is the folder name and a hash of its files.

The privacy policy lists every field, and a test checks that list against the code.

It never sends

• Environment variable values or header values
• The value of any flag, or any word on the command line other than the program name, a few ordinary flag names and the item's own package name
• Folder paths, the names of files inside a skill, or file contents
• Passwords, keys or logins in web addresses
• Your computer name or user name. It sends a hash of the two instead, and we store only a second hash that is different for every company

If a value looks like a secret, the command leaves it out. Our server also refuses a report that still holds one, and stores nothing from it.

See it before it is sent

node agentarmor.mjs inventory --dry-run

This prints the exact data and sends nothing. Run it on a test laptop before any rollout.

What it needs

It needs no admin rights and runs as the signed-in user, with Node 18 or newer. When the laptop joins your organization, it saves a device token in ~/.agentarmor/device.json. On macOS and Linux, only that user can read the file.

It runs, then stops, and leaves no program running. For a daily report, the command "inventory schedule" adds one daily job for that user to the computer's own scheduler. "inventory schedule --remove" takes it out.

Your device-management tool can start the command instead. The command starts no other program except that scheduler (launchctl, crontab, systemctl or schtasks), and only when you run "inventory schedule".

Read the file before you run it

The command is one file you can download and read. Each release is frozen: the same version always gives the same file, and its SHA-256 is published here and at /api/cli/sha256.

Current version 1.1.2
SHA-256 57cef54bfca333844e6b5193123efc0febddc3ff88e5b9cc849f551c7f42092d

curl -fsSL "https://agentarmorhq.com/api/cli?v=1.1.2" -o agentarmor.mjs
shasum -a 256 agentarmor.mjs

curl.exe -fsSL "https://agentarmorhq.com/api/cli?v=1.1.2" -o agentarmor.mjs
Get-FileHash agentarmor.mjs -Algorithm SHA256

Review it, and put your reviewed copy on your own file share if you like.

Where the data lives and who sees it

Reports are sent over HTTPS and stored in our database, hosted by Supabase in the United States, in the us-west-2 region (Oregon).

Your own organization's owners and admins see your laptops and items. Every organization is kept apart in the database.

Each token works for one organization, and the server takes the organization from the token, never from the request. Our tests try to read and change one company's data from another, and expect every attempt to fail.

At WalouTech, only the staff who run the service can reach customer data. They do it for support or security, and only when needed.

Delete or remove

• The whole organization. An owner deletes it in the dashboard, after typing its name to confirm. Everything we store for it is removed from our database at once. Backups and server logs expire on their normal schedule, and Stripe keeps its own invoice records.
• A laptop. An admin removes it in the dashboard. Its token stops working at once, and it is refused from then on.
• A person. An admin removes them in the dashboard. Their sessions end at once.
• A token. Revoke any token at any time, with or without the laptops it enrolled.

Start with no laptop installs

You do not need the laptop command to begin. Build the approved list, export rules for your AI tools, and turn on the pull-request check in your own GitHub.

The check reads config files in the repository. It sends back the repository name, the commit, the policy revision, the mode, the result, the counts, and the identifiers of the items that failed.

What we do not claim

We hold no SOC 2 or ISO certificate. The laptop command sees what is in config files. It cannot see a server someone starts by hand.

Who we are

AgentArmor is a product of WalouTech. Contact: info@agentarmorhq.com.

Report a security issue

Email info@agentarmorhq.com with “Security” in the subject, or use our contact form. Tell us what you found and how to repeat it. We reply within 2 business days.

Our security.txt points here too.