get_product_by_sku
AI agents call get_product_by_sku to retrieve information from Remote MCP Server (Authless) without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name and context strongly suggest it retrieves product information by SKU. Despite the empty description, the 'get_' prefix and analogy to sibling tools imply a query/fetch operation with no side effects. Confidence is moderate rather than high due to lack of explicit description; if the tool actually modifies data or executes commands despite its name, the classification could change.
From the tool's definition Tool named 'get_product_by_sku' with no description provided; naming convention ('get_*') and sibling tools ('get_bestsellers', 'get_products_by_ids', 'get_sales_data') all indicate read-only data retrieval operations.
Attacks that exploit this kind of access
get_product_by_sku. It is categorised as a Read tool in the Remote MCP Server (Authless) MCP Server, which means it retrieves data without modifying state.
Register the Remote MCP Server (Authless) MCP server in PolicyLayer and add a rule for get_product_by_sku: 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 Remote MCP Server (Authless). Nothing to install.
get_product_by_sku 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_by_sku 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_by_sku. 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_by_sku is provided by the Remote MCP Server (Authless) MCP server (roby0404/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 →