search
Search this game development outsourcing directory and return matching documents — studio profiles, buyer guides, ranked lists and the statistics page — as citable {id, title, url} results. Pass the id of any result to "fetch" to read it in full. Prefer "search_studios" when you need structured s...
This record as markdown: /tools/com-gamedevoutsourcing-www-directory/search.md
What search does on Game Dev Outsourcing Directory
AI agents call search 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 |
|---|---|---|---|
query | string | Yes | What to look for. A plain sentence works — "3D character art studios in Poland", "how do I vet a game art studio", "how many studios are in Ukraine". |
Parameters from the server's own tool schema.
Why search is rated Low
Even though search 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 search 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 search, this is the rule to start with:
search 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 search call is checked against it from then on.
Questions about search
Search this game development outsourcing directory and return matching documents — studio profiles, buyer guides, ranked lists and the statistics page — as citable {id, title, url} results. Pass the id of any result to "fetch" to read it in full. Prefer "search_studios" when you need structured studio fields such as services, engine or country. It is categorised as a Read tool in the Game Dev Outsourcing Directory MCP Server, which means it retrieves data without modifying state.
search accepts 1 parameter: query. Required: query. 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 search: 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.
search 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 search 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 search. 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.
search 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