memory_stats
Show your memory usage: total entries, total bytes, namespace count, TTL'd count, pinned count, quota remaining, per-namespace breakdown. Registered handle + secret required.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/memory-stats.md
What memory_stats does on Gateway
AI agents call memory_stats 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 |
|---|---|---|---|
handle | string | Yes | |
secret | string | — |
Parameters from the server's own tool schema.
Why memory_stats is rated Low
This tool retrieves and displays memory usage metrics and statistics. It requires authentication (handle + secret) but performs no data modification, deletion, or execution. The verb 'Show' and the nature of returning usage breakdown data clearly indicate a Read operation.
From the tool's definition Tool description states 'Show your memory usage' — a pure read/query operation that displays statistics about memory consumption without modifying, deleting, or executing anything. No side effects.
Risk signalsHandles credentials or secrets (secret)
Attacks that exploit this kind of access
The rule that runs memory_stats 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 memory_stats, this is the rule to start with:
memory_stats 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 memory_stats call is checked against it from then on.
Questions about memory_stats
Show your memory usage: total entries, total bytes, namespace count, TTL'd count, pinned count, quota remaining, per-namespace breakdown. Registered handle + secret required. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
memory_stats accepts 2 parameters: handle, secret. Required: 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 memory_stats: 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.
memory_stats 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 memory_stats 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 memory_stats. 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.
memory_stats 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