AI agents call tm_list_history to retrieve information from Tm without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list' prefix strongly suggests this tool queries and returns historical data without modifying state. While the empty description reduces confidence slightly, the semantic meaning of 'list_history' in a load-testing/CI-triage context implies retrieving run history or logs. No evidence of write, delete, execute, or financial operations.
From the tool's definition Tool name 'tm_list_history' indicates a retrieval/listing operation. The naming pattern (list_*) is consistent with read-only data access. No description provided to suggest side effects.
Attacks that exploit this kind of access
tm_list_history. It is categorised as a Read tool in the Tm MCP Server, which means it retrieves data without modifying state.
Register the Tm MCP server in PolicyLayer and add a rule for tm_list_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 Tm. Nothing to install.
tm_list_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 tm_list_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 tm_list_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.
tm_list_history is provided by the Tm MCP server (trafficmorph-gif/tm-mcp). 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 →