read_memory_changes
Incremental sync: returns memory entries that have been created, updated, or deleted since the given timestamp. Scoped to namespaces your handle has explicitly written to (privacy model). Registered handle + secret required.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/read-memory-changes.md
What read_memory_changes does on Gateway
AI agents call read_memory_changes to retrieve information from Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | max results (default 50, max 200) |
since | string | Yes | ISO 8601 timestamp |
handle | string | Yes | |
secret | string | — | |
namespace | string | — | optional filter to one namespace |
Parameters from the server's own tool schema.
Why read_memory_changes is rated Low
This tool retrieves incremental changes to memory entries since a timestamp. It performs no mutations, deletions, or external operations—purely a scoped read operation. The privacy model limiting scope to the caller's own namespaces further reduces severity. Classified as Read with low severity due to limited blast radius and no data modification capability.
From the tool's definition Tool description states it 'returns memory entries' - a query/retrieval operation with 'no side effects'. The verb 'returns' and the scope restriction to 'namespaces your handle has explicitly written to' confirm this is a read-only data retrieval mechanism.
Risk signalsHandles credentials or secrets (secret)
Attacks that exploit this kind of access
The rule that runs read_memory_changes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For read_memory_changes, this is the rule to start with:
read_memory_changes is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every read_memory_changes call is checked against it from then on.
Questions about read_memory_changes
Incremental sync: returns memory entries that have been created, updated, or deleted since the given timestamp. Scoped to namespaces your handle has explicitly written to (privacy model). Registered handle + secret required. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
read_memory_changes accepts 5 parameters: limit, since, handle, secret, namespace. Required: since, handle. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for read_memory_changes: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Gateway. Nothing to install.
read_memory_changes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the read_memory_changes rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for read_memory_changes. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
read_memory_changes is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue