# get_directory_statistics

Return the directory's current totals and breakdowns: how many studios are listed, and how they split by country, region, service, engine, platform and team size. Use for any "how many studios..." or "which country has the most..." question, and quote these figures rather than counting search results yourself — they are recomputed from the live database and the counts move.

Agent View of the PolicyLayer registry record for `get_directory_statistics`. HTML page: https://policylayer.com/tools/com-gamedevoutsourcing-www-directory/get-directory-statistics

## Facts

- Tool: `get_directory_statistics`
- Server: Game Dev Outsourcing Directory (`https://www.gamedevoutsourcing.com/api/mcp`) — https://policylayer.com/tools/com-gamedevoutsourcing-www-directory.md
- Homepage: https://github.com/quodsoler/gamedev-connect
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_directory_statistics",
    "arguments": {}
  }
}
```

## Why get_directory_statistics is rated Low

Even though get_directory_statistics 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.

## Use case

AI agents call get_directory_statistics 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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Game Dev Outsourcing Directory:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_directory_statistics": {}
  }
}
```

## Other tools on Game Dev Outsourcing Directory (9)

- `estimate_project_cost` — Read — https://policylayer.com/tools/com-gamedevoutsourcing-www-directory/estimate-project-cost.md
- `fetch` — Read — https://policylayer.com/tools/com-gamedevoutsourcing-www-directory/fetch.md
- `get_answer` — Read — https://policylayer.com/tools/com-gamedevoutsourcing-www-directory/get-answer.md
- `get_ranking` — Read — https://policylayer.com/tools/com-gamedevoutsourcing-www-directory/get-ranking.md
- `get_studio` — Read — https://policylayer.com/tools/com-gamedevoutsourcing-www-directory/get-studio.md
- `list_answers` — Read — https://policylayer.com/tools/com-gamedevoutsourcing-www-directory/list-answers.md
- `list_rankings` — Read — https://policylayer.com/tools/com-gamedevoutsourcing-www-directory/list-rankings.md
- `search` — Read — https://policylayer.com/tools/com-gamedevoutsourcing-www-directory/search.md
- `search_studios` — Read — https://policylayer.com/tools/com-gamedevoutsourcing-www-directory/search-studios.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-gamedevoutsourcing-www-directory · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-gamedevoutsourcing-www-directory