igdb_get_company
Get a game company from IGDB by name or ID.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/igdb-get-company.md
What igdb_get_company does on UnClick
AI agents call igdb_get_company to retrieve information from UnClick 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 |
|---|---|---|---|
name | string | — | Company name to search for |
client_id | string | — | |
company_id | string | — | IGDB company ID (takes precedence over name) |
client_secret | string | — |
Parameters from the server's own tool schema.
Why igdb_get_company is rated Low
This tool retrieves company information from the IGDB (Internet Game Database) API. It performs a lookup/fetch operation without any capability to modify, delete, or execute arbitrary code. The operation is non-destructive and has no financial implications. Even if an agent misuses this by querying many times, the blast radius is minimal - it retrieves publicly available game company data with no side effects.
From the tool's definition Tool description states 'Get a game company from IGDB by name or ID' - the verb 'Get' and the retrieval operation (no modification or deletion described) indicate this is a read-only query operation.
Attacks that exploit this kind of access
The rule that runs igdb_get_company safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For igdb_get_company, this is the rule to start with:
igdb_get_company 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 UnClick, apply this rule, and every igdb_get_company call is checked against it from then on.
Questions about igdb_get_company
Get a game company from IGDB by name or ID. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
igdb_get_company accepts 4 parameters: name, client_id, company_id, client_secret. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for igdb_get_company: 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 UnClick. Nothing to install.
igdb_get_company 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 igdb_get_company 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 igdb_get_company. 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.
igdb_get_company is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue