AI agents call get_rsuser_total to retrieve information from Runescape without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool simply retrieves and returns a read-only count/statistic about existing RuneScape accounts. There are no side effects, no data modification, no code execution, and no destructive actions. It is a straightforward data query operation, making it a Read category tool with low severity since misuse would only expose publicly available statistical information.
From the tool's definition Tool name 'get_rsuser_total' and description 'Returns the current amount of accounts created' indicates a data retrieval operation querying aggregate account statistics with no modification, creation, deletion, or execution of code.
Attacks that exploit this kind of access
Returns the current amount of accounts created that can access any form of RuneScape. This includes accounts made on FunOrb or a particular version of RuneScape. It is categorised as a Read tool in the Runescape MCP Server, which means it retrieves data without modifying state.
Register the Runescape MCP server in PolicyLayer and add a rule for get_rsuser_total: 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 Runescape. Nothing to install.
get_rsuser_total 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_rsuser_total 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_rsuser_total. 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_rsuser_total is provided by the Runescape MCP server (mcp-server-runescape). 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 →