get_messages
AI agents call get_messages to retrieve information from Containerized Strands Agents without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves conversation messages from agent workspaces. While the description is empty, the name strongly suggests a read-only query operation. The blast radius is minimal—even if an AI agent over-fetches messages, no data is modified or external operations triggered.
From the tool's definition Tool name 'get_messages' indicates retrieval of conversation history or message records without modification. No destructive, financial, or side-effect operations implied.
Attacks that exploit this kind of access
get_messages. It is categorised as a Read tool in the Containerized Strands Agents MCP Server, which means it retrieves data without modifying state.
Register the Containerized Strands Agents MCP server in PolicyLayer and add a rule for get_messages: 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 Containerized Strands Agents. Nothing to install.
get_messages 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_messages 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_messages. 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_messages is provided by the Containerized Strands Agents MCP server (mkmeral/containerized-strands-agents). 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 →