Get product information by product ID
AI agents call get-product-info to retrieve information from Ecommerce Store without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves product data based on an identifier and has no side effects. It falls clearly into the Read category as a straightforward data query operation. The severity is low because misuse (e.g., querying many products) would have minimal impact on an ecommerce system—at worst, it could cause minor performance issues or expose catalog information already intended to be public.
From the tool's definition Tool name and description indicate retrieval only: 'Get product information by product ID' with no mention of modification, deletion, or side effects. This is a simple lookup operation against a product catalog.
Attacks that exploit this kind of access
Get product information by product ID. It is categorised as a Read tool in the Ecommerce Store MCP Server, which means it retrieves data without modifying state.
Register the Ecommerce Store MCP server in PolicyLayer and add a rule for get-product-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 Ecommerce Store. Nothing to install.
get-product-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-product-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-product-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-product-info is provided by the Ecommerce Store MCP server (khesayed/ecommerce-store-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 →