# unwalled lets your AI assistant look up orders

Canonical: https://www.kartikaydhar.com/blog/unwalled-app-requests-mcp-tools
Published: 2026-11-08T04:11:44.439+00:00
Updated: 2026-11-08T04:11:29.738852+00:00
Category: Tool Breakdowns

unwalled records how an app looks up information so an AI assistant can repeat it. I tried the local demo and checked its access risks.

unwalled is a free, open-source tool from KorroAi that lets an AI assistant look up information in a web app. When you open an order, the page asks a server for its details. unwalled records how that lookup works so your assistant can repeat it without opening the order page each time.

It connects the app to your assistant through Model Context Protocol (MCP), a standard for calling tools. For a product manager, that could mean asking for an order's status in an internal back office that has no ready-made connection to your assistant.

I tried v0.5.1 with the project's local Acme demo. I retrieved order 1042, marked paid with a total of 880, and a list of five customers in Lyon. These were fake records in a sample app running on the same computer, not a real company's account. The order result does not name a currency or unit.

## What I tested

I used a small test program to connect through MCP, list the available tools and make the two lookups. The demo had signed in with its sample account, opened an order and visited two customer pages. I also ran its tool health check and tried importing a CSV file.

That shows how unwalled can give an assistant access to an app's data. It does not test the quality of an AI assistant's answers. My test program called the tools directly.

## How would I try it safely?

I would start with the built-in demo, before connecting an account with real data. The setup below comes from the official README and installation guide. It is a documented route using Cursor, which the project supports; my measured lookups used the test program described above.

- Ask an engineer to install Node.js and check the browser. The project requires Node 22 or newer. Local file imports need the node:sqlite feature from Node 22.5 or newer, so use a supported release that meets both requirements. Browser capture needs Chrome, Edge or the Chromium option described in the guide.
- Have the engineer run the guided setup in a terminal, the window where you type commands:npx -y unwalled
- The setup checks the computer and offers to add unwalled to supported AI apps it finds. For this route, approve adding it to Cursor. It asks separately for each app; you do not need to connect every app it finds.
- Follow the setup's instructions for loading the change in Cursor. The guide says setup explains whether an app needs a new session or a restart. If it cannot edit an existing configuration file, it shows the entry for an engineer to add. Choose the demo as the first source. The README says this starts and connects a sample back office with orders and customers behind a sign-in. Keep the demo running while you try it.
- Before making calls, have the engineer review the generated tools and apply read-only access. The documented settings include policy.readOnly and policy.allowedHosts, which restrict changes and the sites tools may contact. Review any tool-use approval your assistant asks for; do not give it blanket permission to change records.
- In Cursor, ask the README's demo question:

Using acme, what is the status and total of order 1042? And which customers are in Lyon?

In my demo, order 1042 was paid, its total was 880, and the customer table had five Lyon rows. Compare the returned records with the sample app, rather than accepting the assistant's wording alone. Your engineer should check the connection if the tools are missing; installing instructions is not the same as confirming a working connection.

The PM's job is to choose the question, know what a correct answer looks like and decide which information the assistant may read. The engineer handles installation, connection and access rules. Once the demo works, a sensible next exercise is one known lookup in a test copy of your app, with fake records and a read-only account. That is a suggested trial, separate from my measured demo.

## What is unwalled saving?

For your own app, you sign in and open the pages your assistant will need. unwalled watches how those pages talk to their server. It saves a description of the available actions and their inputs in a file called a recipe. Think of it as a saved set of directions for doing those lookups.

The demo recorded four requests and made eight tools: four for reading data directly from the app's API, three for reading web pages, and one general request tool. An API is the way software asks other software for data or an action. For a page built as HTML, unwalled can also pull its tables and fields into a structured result.

The recipe describes what the recording revealed. It is not a complete list of everything the app can do. An engineer should check the addresses and inputs unwalled inferred before giving an assistant access. The docs say that inference can make mistakes.

## Can the assistant change things in my account?

The assistant's tools can act with the account you signed in to. If that account can change records, access needs more care than a simple order lookup. Generated tools are not automatically read-only.

The demo's general tool, acme__request, can send requests beyond the named lookups. The reference says it accepts an absolute URL or a path on the saved app, using the recipe's cookies and credentials under its policies. Have an engineer review it along with the narrower tools. The security guide says credentials are sent only to the host they belong to.

By default, unwalled asks for confirmation for DELETE requests and risky clicks in the interface. That does not mean every change needs approval. To require confirmation for every write, the documented setting is UNWALLED_CONFIRM=writes. For a lookup-only trial, I would use the read-only policy as well as an account that cannot change data.

An engineer can preview a tool call with dry_run before sending it; the preview hides credentials. For teams, the docs describe administrator-set rules that the assistant cannot loosen, covering read-only access, allowed sites, confirmations, disabled tools and required audit logs. These are documented safeguards, not controls I proved with my two reads.

Use only apps you are allowed to automate, and prefer an official connection when one exists. A private app address discovered during browsing is not a promise that the app owner supports outside use. The docs also warn that some requests signed by the page's own code cannot be repeated from a recording.

## Where do sign-in details go?

When your assistant retrieves order or customer records to answer a question, those results can be sent to its AI model, depending on the assistant and model you use. Keeping passwords and cookies on your computer does not mean the business records stay there.

Keep unwalled's saved data private. The security guide says recipes hold addresses, data descriptions and examples with secrets removed. Passwords and other secrets, saved session cookies and local state are encrypted with AES-256-GCM. This is not a claim that every part of the browser profile is encrypted.

The guide warns that on systems using its fallback key file, the encryption key sits beside the saved data. Someone who can read that folder can also read the key. Protect the folder and keep browser profiles, secrets and state out of shared folders and source control.

Secret detection can miss things, so inspect a recipe before sharing it. The audit log records details such as the tool used, address with secrets hidden and response status. It does not record request bodies or credentials.

## What did the local test return?

The tested version was v0.5.1, matching npm and the repo's package metadata when I checked. These timings are single observations from the local demo. They do not predict a real service's speed or measure AI model cost.

- Connect test programResult: 27 tools listed afterwards
- Time: 1,213 ms
- Read order 1042Result: HTTP 200; paid; total 880
- Time: 343 ms
- Read Lyon customer listResult: HTTP 200; five rows
- Time: 15 ms
- Check saved readsResult: Seven tools returned HTTP 200
- Time: 2.578 s
- The connection timer includes starting npx -y unwalled serve and making the MCP connection. Listing tools came after that timer stopped. The list had 19 management tools plus eight generated tools.
- The lookup timers cover the test program's tool call and gathering its returned text. They are not isolated server timings. The order's line items add up to 880: one at 204 and two at 338.
- The health check covered four API readers and three page readers. All returned HTTP 200, a successful response. The general acme__request tool was not checked. The docs say checks cover read-only tools with recorded examples and never test writes. The 2.578 seconds covers the whole check command, not seven separately timed calls.
- I ran it on Node 20.19.2. The CSV import failed because local data needs node:sqlite from Node 22.5 or newer. It was not a successful import, and a working demo on Node 20 does not make that runtime supported.

## What this means for product and GTM teams

I would use the first trial to decide whether a repeated lookup is useful enough to maintain. Someone must own the saved directions when the app changes, and someone must review the account access. A passing health check helps find broken reads; it does not settle either decision.

Choose one question before granting access to a whole back office. The distinction between instructions and access to tools is explained in Agent Skills and MCP. The related WebMCP explanation covers how a website can deliberately expose actions for assistants.

## Frequently asked questions

### Is unwalled free?

The software is open source under Apache License 2.0, with no licence fee for the local package. Your assistant or model, the computer running it and any connected service can have separate costs. My logs do not measure model spend.

### Do I need to know how to code?

You can choose the question and check the answer without writing code. An engineer should help with installation, the assistant connection and account permissions before you use real data.

### Does it work with every web app?

No. It needs a usable way to repeat the app's lookups or read its pages. Captured private APIs can change, and some page-signed requests cannot be repeated directly.

### Does it only read data?

No. Apply read-only rules for a lookup-only assistant. The default confirmation rule covers DELETE requests and risky interface clicks; requiring approval for all writes is a separate setting.

## Sources

- Official README: guided setup, supported assistants, built-in demo, first question and licence. Checked 8 Nov 2026.
- Installation guide: connection steps, configuration fallback and app restart instructions.
- Full reference: tools, health checks, policies and limits.
- Security guide: account access, storage and confirmation rules.
- Package metadata and npm package: version and Node requirement.
