Returns the number of players currently online in RuneScape and Old School RuneScape.
AI agents call get_player_count 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 is a straightforward query of public game status data. It reads and returns a single metric (player count) without creating, modifying, deleting, or triggering any operations. The blast radius if misused by an AI agent is negligible—it cannot harm systems, expose sensitive information, or cause any adverse effect.
From the tool's definition Tool name is 'get_player_count' and description states it 'Returns the number of players currently online' — a pure data retrieval operation with no side effects, no data modification, and no external state changes.
Documented attack patterns abuse exactly the kind of access get_player_count gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Runescape, and nothing reaches the server without passing your rules. This is the rule we recommend for get_player_count:
{
"version": "1",
"default": "deny",
"tools": {
"get_player_count": {}
}
}get_player_count is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Returns the number of players currently online in RuneScape and Old School 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_player_count: 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_player_count 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_player_count 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_player_count. 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_player_count is provided by the Runescape MCP server (stjepko-xyz/mcp-server-runescape). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Runescape, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Runescape tools catalogued and risk-classified — across an index of 43,000+ MCP servers.