get-product-details
AI agents call get-product-details to retrieve information from Terminal Shop MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve product details from Terminal.shop's product catalog. This is a read-only query operation with no capacity to modify, delete, or execute code. The empty description lowers confidence slightly, but the semantic meaning of 'get-product-details' in an e-commerce context is unambiguous. Even in misuse scenarios, an agent could only retrieve information about products, posing minimal risk.
From the tool's definition Tool name 'get-product-details' indicates data retrieval. Description is empty, but the name and the context of a shopping API strongly suggest this fetches product information without side effects.
Attacks that exploit this kind of access
get-product-details. It is categorised as a Read tool in the Terminal Shop MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Terminal Shop MCP Server MCP server in PolicyLayer and add a rule for get-product-details: 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 Terminal Shop MCP Server. Nothing to install.
get-product-details 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-product-details 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-product-details. 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-product-details is provided by the Terminal Shop MCP Server MCP server (pashaydev/terminal.shop.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 →