get_item_wear_by_inspect_url
AI agents call get_item_wear_by_inspect_url 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.
This tool retrieves item wear information from an inspect URL, which is a read-only query operation with no side effects. It follows the pattern of sibling tools that all query Steam data without modifying, deleting, or executing external operations. Confidence is slightly reduced due to empty description, but the context is clear.
From the tool's definition Tool name 'get_item_wear_by_inspect_url' and sibling tools (get_item_base_info, get_item_price, get_item_price_history, get_item_wear_by_asmd, search_item_by_name) all perform read-only queries of Steam marketplace data.
Documented attack patterns abuse exactly the kind of access get_item_wear_by_inspect_url 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_inspect_url:
{
"version": "1",
"default": "deny",
"tools": {
"get_item_wear_by_inspect_url": {}
}
}get_item_wear_by_inspect_url 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_inspect_url. 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_inspect_url: 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_inspect_url 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_inspect_url 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_inspect_url. 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_inspect_url 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.