Search affiliate (多多客) goods by keyword.
AI agents call search_affiliate_goods to retrieve information from Pypi:mcp Cn Commerce without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries/retrieves affiliate product data based on a keyword search. Searching is a classic Read category operation—it retrieves information without creating, modifying, deleting, or executing anything. The server explicitly provides 'read-only access', and this tool fits that pattern alongside similar tools like get_inventory and get_live_data.
From the tool's definition Tool is described as 'Search affiliate goods by keyword' and is part of a 'read-only access' server suite. The action of searching is a retrieval operation with no side effects.
Attacks that exploit this kind of access
Search affiliate (多多客) goods by keyword. It is categorised as a Read tool in the Pypi:mcp Cn Commerce MCP Server, which means it retrieves data without modifying state.
Register the Pypi:mcp Cn Commerce MCP server in PolicyLayer and add a rule for search_affiliate_goods: 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 Pypi:mcp Cn Commerce. Nothing to install.
search_affiliate_goods 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 search_affiliate_goods 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 search_affiliate_goods. 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.
search_affiliate_goods is provided by the Pypi:mcp Cn Commerce MCP server (tonywang-hub/mcp-cn-commerce). 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 →