Show the conversation around a specific message id (found in search
AI agents call get_message_context to retrieve information from Rocket Cli without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing message data with no side effects. It retrieves context information from cached messages. Consistent with sibling tools like get_messages, get_thread_messages, and get_mentions, which are all read operations. The low severity reflects that viewing message context poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'get_message_context' and description indicate it retrieves conversation context around a message id. The verb 'show' and 'get' are read operations. No modification, deletion, or execution is described.
Attacks that exploit this kind of access
Show the conversation around a specific message id (found in search. It is categorised as a Read tool in the Rocket Cli MCP Server, which means it retrieves data without modifying state.
Register the Rocket Cli MCP server in PolicyLayer and add a rule for get_message_context: 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 Rocket Cli. Nothing to install.
get_message_context 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_message_context 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_message_context. 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_message_context is provided by the Rocket Cli MCP server (jeanfbrito/rocket-cli). 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 →