AI agents call rms_product_ranking to retrieve information from Rms 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 sales ranking data. It is a read-only query that fetches existing sales data without any side effects, modifications, or destructive actions.
From the tool's definition Product sales ranking by revenue (from PackageModelList)
Attacks that exploit this kind of access
Product sales ranking by revenue (from PackageModelList). It is categorised as a Read tool in the Rms MCP Server, which means it retrieves data without modifying state.
Register the Rms MCP server in PolicyLayer and add a rule for rms_product_ranking: 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 Rms. Nothing to install.
rms_product_ranking 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 rms_product_ranking 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 rms_product_ranking. 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.
rms_product_ranking is provided by the Rms MCP server (yasuhidekoizumi-afk/rms-mcp). 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 →