get_after_sale_list
AI agents call get_after_sale_list 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.
The tool retrieves after-sales list data without modification capability. Server documentation explicitly states 'read-only access,' and the naming convention (get_*) is consistent with data retrieval. No evidence of side effects, deletion, execution, or financial operations. Low severity due to limited blast radius from querying business data alone.
From the tool's definition Tool named 'get_after_sale_list' with context indicating 'read-only access' to e-commerce data; sibling tools like 'get_after_sale_detail', 'get_inventory', 'get_metrics' are all retrieval operations.
Attacks that exploit this kind of access
get_after_sale_list. 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 get_after_sale_list: 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.
get_after_sale_list 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_after_sale_list 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_after_sale_list. 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_after_sale_list 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 →