memory_get
AI agents call memory_get to retrieve information from AWS IoT SiteWise MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get' verb combined with 'memory' in the tool name suggests data retrieval. Without a description, confidence is reduced, but 'get' operations are conventionally read-only. No evidence of modification, deletion, execution, or financial impact is apparent from the name alone. If this tool unexpectedly performs writes or destructive operations, the classification should be revisited with proper documentation.
From the tool's definition Tool name 'memory_get' indicates a retrieval operation. The description is empty, preventing definitive classification, but the naming convention strongly suggests a read operation that retrieves data from memory without side effects.
Attacks that exploit this kind of access
memory_get. It is categorised as a Read tool in the AWS IoT SiteWise MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for memory_get: 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 AWS IoT SiteWise MCP Server. Nothing to install.
memory_get 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_get 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_get. 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_get is provided by the AWS IoT SiteWise MCP Server MCP server (awslabs.aws-iot-sitewise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.