List message history optionally since a date
AI agents call get_message_history to retrieve information from Multi-MCPs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical message data with optional filtering by date. It performs a query operation with no side effects, no data modification, no code execution, and no destructive capability. The action is purely informational retrieval, making it a Read category tool with low severity.
From the tool's definition Tool name 'get_message_history' and description 'List message history optionally since a date' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
List message history optionally since a date. It is categorised as a Read tool in the Multi-MCPs MCP Server, which means it retrieves data without modifying state.
Register the Multi-MCPs MCP server in PolicyLayer and add a rule for get_message_history: 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 Multi-MCPs. Nothing to install.
get_message_history 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_history 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_history. 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_history is provided by the Multi-MCPs MCP server (taylorchen/muti-mcps). 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 →