get_studio
Return one studio's full directory listing by its slug: description, services, engines, platforms, art styles, spoken languages, team size, location, and its positions on any of this directory's ranked lists. Use after search_studios when you need detail on one studio, or when the user names a st...
This record as markdown: /tools/com-gamedevoutsourcing-www-directory/get-studio.md
What get_studio does on Game Dev Outsourcing Directory
AI agents call get_studio to retrieve information from Game Dev Outsourcing Directory without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
slug | string | Yes | The studio's slug, the last part of its profile URL — "room-8-studio" from /company/room-8-studio. A full URL is accepted. |
Parameters from the server's own tool schema.
Why get_studio is rated Low
Even though get_studio 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.
Attacks that exploit this kind of access
The rule that runs get_studio safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Game Dev Outsourcing Directory, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_studio, this is the rule to start with:
get_studio is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Game Dev Outsourcing Directory, apply this rule, and every get_studio call is checked against it from then on.
Questions about get_studio
Return one studio's full directory listing by its slug: description, services, engines, platforms, art styles, spoken languages, team size, location, and its positions on any of this directory's ranked lists. Use after search_studios when you need detail on one studio, or when the user names a studio whose gamedevoutsourcing.com slug you already have. Contact details are not available here. It is categorised as a Read tool in the Game Dev Outsourcing Directory MCP Server, which means it retrieves data without modifying state.
get_studio accepts 1 parameter: slug. Required: slug. The full parameter table on this page comes from the server's own tool schema.
Register the Game Dev Outsourcing Directory MCP server in PolicyLayer and add a rule for get_studio: 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 Game Dev Outsourcing Directory. Nothing to install.
get_studio 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_studio 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_studio. 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_studio is provided by the Game Dev Outsourcing Directory MCP server (https://www.gamedevoutsourcing.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Game Dev Outsourcing Directory, and thousands of servers like it.
This server
Across the catalogue