A pre-audit sweep
Maya Okafor, compliance manager at BigCo, asked how ready they were for SOC 2. Memtro read the framework's passing, failing and at-risk test counts. It then listed the failing tests with their owners and recommended actions.
Which tests are failing, and has everyone accepted the security policy?
Secureframe tracks your compliance work, and Memtro reads it so you can ask in plain words. It reads tests that pass, fail or are at risk, controls, frameworks, policy acceptance, risks, vendors by risk level and compliance tasks. Risk notes and vendor contacts are never returned. When asked, and once an administrator has granted the action by name, it can comment on records, create or disable tests, open and update POA&M items and add knowledge base questions. Comments are visible to auditors. Deleting a comment, discarding a POA&M item and archiving a vendor are permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Secureframe tool, reads what it needs, and answers with the source cited.
These tools change something in Secureframe. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Secureframe is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Which tests are failing?
Has everyone accepted the security policy?
How ready are we for SOC 2?
Which high-risk vendors have two-factor off?
Open a POA&M item for the failing backup test, owned by Maya Okafor
Maya Okafor, compliance manager at BigCo, asked how ready they were for SOC 2. Memtro read the framework's passing, failing and at-risk test counts. It then listed the failing tests with their owners and recommended actions.
Dan Fletcher, operations director at Acme Ltd, asked Memtro to open a POA&M item for the failing encryption test and assign it to Maya Okafor. Memtro opened the item as a draft with a low risk level under her name, and it appeared in Secureframe's plan of action for the auditors to see.
The teams that lean on Secureframe most, a question each of them asks, and what they connect beside it.
A record in Secureframe is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In Secureframe, sign in as a user whose role can see tests, controls, frameworks, policies, risks, vendors and tasks. For the actions, the role also needs write access to comments, tests, POA&M, vendors and the knowledge base as needed.
Open Your profile → Company settings → API keys, create an API key and copy the key and its secret. The secret is shown once.
In Memtro, open Connections → Secureframe and paste API key and API secret. Set Region to uk if your account is hosted in the UK.
Ask: which tests are failing?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Secureframe tools are the same everywhere.
Only when you ask, and only what it has been granted: comment on a test, control, risk, policy, POA&M item, evidence or vendor review in Secureframe; edit a Secureframe comment; delete a Secureframe comment; create a custom upload test in Secureframe; enable or disable a Secureframe test, or change its owner, due date or interval; open a POA&M item in Secureframe; update a Secureframe POA&M item; discard a Secureframe POA&M item; archive a vendor in Secureframe; add a question to the Secureframe knowledge base. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
API key and API secret, plus region. In Secureframe, sign in as a user whose role can see tests, controls, frameworks, policies, risks, vendors and tasks. For the actions, the role also needs write access to comments, tests, POA&M, vendors and the knowledge base as needed.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time