Get completed trade history with partner names. Requires API key with trade permissions.
AI agents call get_trade_history to retrieve information from Steam MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool fetches past transaction records from Steam's inventory trading system. While it is purely retrievable (Read category), the severity is elevated to medium because trade history can reveal sensitive economic and relationship data about a player (who they trade with, what items/values, timing patterns), which could enable social engineering, financial profiling, or account targeting if exposed to an…
From the tool's definition Tool retrieves 'completed trade history with partner names' — a query operation that returns historical data without modifying, deleting, or executing operations. The 'Get' verb and 'history' designation indicate read-only access.
Attacks that exploit this kind of access
Get completed trade history with partner names. Requires API key with trade permissions. It is categorised as a Read tool in the Steam MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Steam MCP Server MCP server in PolicyLayer and add a rule for get_trade_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 Steam MCP Server. Nothing to install.
get_trade_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_trade_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_trade_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_trade_history is provided by the Steam MCP Server MCP server (sharkusmanch/steam-mcp-server). 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 →