List all products with optional filtering
AI agents call list_products to retrieve information from MCP Product Management System without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays product information from the inventory database. It has no side effects, does not modify data, and presents no financial or destructive risk. The filtering capability is a read-only query operation. Grouped with sibling tools like 'search_products', 'get_product', and 'get_categories', this clearly belongs in the Read category with low severity.
From the tool's definition Tool name 'list_products' and description 'List all products with optional filtering' indicates retrieval of product data with no modification or deletion. The 'optional filtering' capability is a standard query parameter feature typical of read operations.
Attacks that exploit this kind of access
List all products with optional filtering. It is categorised as a Read tool in the MCP Product Management System MCP Server, which means it retrieves data without modifying state.
Register the MCP Product Management System MCP server in PolicyLayer and add a rule for list_products: 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 MCP Product Management System. Nothing to install.
list_products 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 list_products 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 list_products. 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.
list_products is provided by the MCP Product Management System MCP server (pysorflow/mcpdemo). 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 →