Low Risk

get_game_details

Fetch full details for a specific game given its ROM page URL. Returns size, year, region, genre, languages, rating, serial number, description, and cover image. Args: url: The game page URL from a search_roms result (vimm.net, romsgames.net, cdromance.org, or lolroms.com)

How to control get_game_details ↓

AI agents call get_game_details to retrieve information from Romulus 31780 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
url string

Parameters from the server's own tool schema.

Low Risk

Even though get_game_details only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsAccepts URL/endpoint input (url)

Documented attack patterns abuse exactly the kind of access get_game_details gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Romulus 31780, and nothing reaches the server without passing your rules. This is the rule we recommend for get_game_details:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_game_details": {}
  }
}

get_game_details is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Romulus 31780 — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_game_details tool do? +

Fetch full details for a specific game given its ROM page URL. Returns size, year, region, genre, languages, rating, serial number, description, and cover image. Args: url: The game page URL from a search_roms result (vimm.net, romsgames.net, cdromance.org, or lolroms.com). It is categorised as a Read tool in the Romulus 31780 MCP Server, which means it retrieves data without modifying state.

What parameters does get_game_details accept? +

get_game_details accepts 1 parameter: url. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_game_details? +

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

What risk level is get_game_details? +

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

Can I rate-limit get_game_details? +

Yes. Add a rate_limit block to the get_game_details 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 get_game_details completely? +

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

get_game_details is provided by the Romulus 31780 MCP server (openclaw-hal9000/romulus-31780). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Romulus 31780 tool call.

Deterministic rules across all 3 Romulus 31780 tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

3 Romulus 31780 tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.