services_query

Read from Sandbox.Services — the cloud stats/leaderboard layer many games use as their real DB. action=

SERVERSbox SOURCEsbox-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sbox/services-query.md

WHAT IT DOES

What services_query does on Sbox

AI agents call services_query to retrieve information from Sbox without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why services_query is rated Low

This tool retrieves data from a cloud service (stats/leaderboards) without modifying it. While categorized as Read, severity is medium rather than low because: (1) leaderboard/stats systems may contain user data or competitive information that could be sensitive; (2) the incomplete description ('action=') suggests flexible query capabilities that could access various data types; (3) in a game context, unbounded read…

From the tool's definition Tool description states 'Read from Sandbox.Services' and is described as querying 'the cloud stats/leaderboard layer'. The name 'services_query' and explicit 'Read from' language indicate a retrieval operation with no data modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs services_query safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sbox, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For services_query, this is the rule to start with:

services_query Allowed

services_query is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "services_query": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sbox, apply this rule, and every services_query call is checked against it from then on.

FAQ

Questions about services_query

What does the services_query tool do? +

Read from Sandbox.Services — the cloud stats/leaderboard layer many games use as their real DB. action=. It is categorised as a Read tool in the Sbox MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on services_query? +

Register the Sbox MCP server in PolicyLayer and add a rule for services_query: 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 Sbox. Nothing to install.

What risk level is services_query? +

services_query is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit services_query? +

Yes. Add a rate_limit block to the services_query 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.

How do I block services_query completely? +

Set action: deny in the PolicyLayer policy for services_query. 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.

What MCP server provides services_query? +

services_query is provided by the Sbox MCP server (sbox-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sbox, and thousands of servers like it.

This server

All 207 Sbox tools →

Across the catalogue

claude_query on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →