商品詳細情報取得 - 商品コードを指定して詳細情報を取得
AI agents call get_product_details to retrieve information from ProductMaster MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool's function is purely to fetch and return product details based on a product code identifier. There are no side effects, data modifications, deletions, financial transactions, or code execution involved. This is a straightforward read operation on a product database, similar to a GET request in REST APIs.
From the tool's definition Tool description indicates 'retrieve detailed information' by specifying a product code ("商品詳細情報取得 - 商品コードを指定して詳細情報を取得" translates to 'Get product detailed information - retrieve detailed information by specifying a product code').
Attacks that exploit this kind of access
商品詳細情報取得 - 商品コードを指定して詳細情報を取得. It is categorised as a Read tool in the ProductMaster MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ProductMaster 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 ProductMaster 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 ProductMaster MCP Server MCP server (takehig/productmaster-mcp-server). 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 →