Memory scope check
wever_memory-scope-checkAgent Memory: submit an agent’s memory design: the scope (whether it is written down, the categories kept, the categories excluded by rule, whether memory is kept per principal, in one global store every principal shares or a mix, the retention headline, and whether a written rule, the model’s own judgment or both decide each write), optionally each category with its kind (facts about the principal, task history, preferences, contacts, credentials, payment details, health details, location, inferences or other), whether it is kept or excluded, what decides it, whether it is kept per principal or shared and why it is kept, and the stored memories seen with their category. The signed report states what is kept, what is excluded by rule and whether the keeping is per principal or global, and names no scope, writes decided by the model, nothing excluded, one global store every principal shares and every stored memory in an excluded category, then a scope set only in code, mixed keying, every category kept in the shared store, decided by the model, kept with no purpose or holding credentials, payment or health details, every category both kept and excluded and every memory outside the scope, with the fix for each. This reads what the system keeps: which stores hold run state and which hold cross-session memory is wever_memory-design-check, whether the principal agreed to be remembered and stays in control is wever_memory-consent-check and how long memory is kept is wever_memory-retention-check. A summary sample is wever_memory-scope-sample on https://weverlabs.com/mcp-free. Verdict keeps_too_much, scope_gaps, scope_unverified or scope_bounded. POST /api/memory-scope-check. Reads only the material in the call: no network request, fetch, money movement, message, sharing, configuration change or external write. Paid URL: 0.10 USDC per call on Base via x402 exact, with the shared 10 signed-wallet free calls per rolling 30 days. Bind X-Wever-Wallet-Proof to the exact JSON arguments and the tool route. Returns a report with an Ed25519 signed receipt. Contract: /api/agent-memory-contract. Human page: https://weverlabs.com/agent-memory/.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "wever_memory-scope-check"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| label | No | Optional name recorded in the report. | |
| scope | No | ||
| system | No | The agent, such as the travel assistant. | |
| memories | No | Stored memories seen, to find writes outside the scope. | |
| categories | No | Each category of memory, kept or excluded. |