get_item_base_info
AI agents call get_item_base_info 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 Steam item base information without modifying data or executing code. While the description is empty (lowering confidence slightly from 0.9 to 0.8), the naming pattern and server context clearly indicate a read-only query operation. No side effects, financial impact, or destructive capability.
From the tool's definition Tool name 'get_item_base_info' combined with server purpose 'retrieving and analyzing Steam marketplace data' and sibling tools that are all read-only queries (get_item_price, get_item_price_history, get_item_wear_by_asmd, search_item_by_name).
Documented attack patterns abuse exactly the kind of access get_item_base_info 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_base_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_item_base_info": {}
}
}get_item_base_info 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_base_info. 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_base_info: 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_base_info 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_base_info 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_base_info. 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_base_info 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.