get_all_memories
AI agents call get_all_memories to retrieve information from Dual MCP Server for IoT & Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name clearly indicates a retrieval/query function ('get_all_') with no implications of modification, deletion, or execution. Even without a description, the pattern is consistent with Read operations that query persistent storage. The empty description reduces confidence slightly, but the naming convention is sufficiently clear to classify this as Read with low severity.
From the tool's definition Tool name 'get_all_memories' indicates a retrieval operation. The description is empty, but sibling tools include 'search_memories' and 'save_memory', suggesting this server manages a memory storage system where get_all_memories would retrieve stored data…
Attacks that exploit this kind of access
get_all_memories. It is categorised as a Read tool in the Dual MCP Server for IoT & Memory MCP Server, which means it retrieves data without modifying state.
Register the Dual MCP Server for IoT & Memory MCP server in PolicyLayer and add a rule for get_all_memories: 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 Dual MCP Server for IoT & Memory. Nothing to install.
get_all_memories 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 get_all_memories 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 get_all_memories. 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.
get_all_memories is provided by the Dual MCP Server for IoT & Memory MCP server (jordy33/iot_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →