get_item_wear_by_asmd
AI agents call get_item_wear_by_asmd to retrieve information from Steamdt without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on naming convention and context from sibling tools, this appears to be a read-only query for Steam item wear data. No description provided reduces confidence, but the tool name pattern and server purpose (querying data) indicate a Read classification. Even if misused, retrieving item wear information poses minimal risk—no data is modified, deleted, or financial operations are triggered.
From the tool's definition Tool name contains 'get_item_wear' suggesting data retrieval. Description is empty, limiting certainty. Sibling tools on the server (get_item_wear_by_inspect_url, get_item_base_info, get_item_price, get_item_price_history) are all Read operations that query…
Documented attack patterns abuse exactly the kind of access get_item_wear_by_asmd gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Steamdt, and nothing reaches the server without passing your rules. This is the rule we recommend for get_item_wear_by_asmd:
{
"version": "1",
"default": "deny",
"tools": {
"get_item_wear_by_asmd": {}
}
}get_item_wear_by_asmd is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_item_wear_by_asmd. It is categorised as a Read tool in the Steamdt MCP Server, which means it retrieves data without modifying state.
Register the Steamdt MCP server in PolicyLayer and add a rule for get_item_wear_by_asmd: 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 Steamdt. Nothing to install.
get_item_wear_by_asmd 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_item_wear_by_asmd 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_item_wear_by_asmd. 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_item_wear_by_asmd is provided by the Steamdt MCP server (kir4kami/mcp-steamdt). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Steamdt, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Steamdt tools catalogued and risk-classified — across an index of 43,000+ MCP servers.