content_catalog
Browse the Gapup gold-standard content catalogue — video games, films, TV series and music. Returns franchises with their works (title, release year). When to use this tool: an agent needs structured, audited metadata for a cultural franchise, wants to resolve a title to a canonical entity, or br...
This record as markdown: /tools/io-github-getgapup-mcp-knowledge/content-catalog.md
What content_catalog does on Mcp Knowledge
AI agents call content_catalog to retrieve information from Mcp Knowledge 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 | — | Optional case-insensitive substring filter on franchise name |
async | boolean | — | If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti |
limit | integer | — | Maximum number of franchises to return (default 20) |
domain | string | Yes | Content domain to browse |
Parameters from the server's own tool schema.
Why content_catalog is rated Low
The tool itself performs only read operations (browse, return, resolve). No data is created, modified, deleted, or financial transactions occur. However, severity is medium rather than low because: (1) the metadata it exposes (franchise IDs, catalogues) could be used by sibling tools for profiling or targeting, and (2) the server context suggests this is part of a larger intelligence/manipulation platform.
From the tool's definition Tool 'content_catalog' is described as allowing agents to 'Browse...content catalogue' and 'Returns franchises with their works' — these are query/retrieval operations with no modification.
Attacks that exploit this kind of access
The rule that runs content_catalog safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Knowledge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For content_catalog, this is the rule to start with:
content_catalog 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 Mcp Knowledge, apply this rule, and every content_catalog call is checked against it from then on.
Questions about content_catalog
Browse the Gapup gold-standard content catalogue — video games, films, TV series and music. Returns franchises with their works (title, release year). When to use this tool: an agent needs structured, audited metadata for a cultural franchise, wants to resolve a title to a canonical entity, or browses a domain's catalogue before requesting enrichment. Inputs: a content domain and an optional case-insensitive name filter. Each franchise id can be passed to content_enrichment for its fine-grained tag profile. It is categorised as a Read tool in the Mcp Knowledge MCP Server, which means it retrieves data without modifying state.
content_catalog accepts 4 parameters: name, async, limit, domain. Required: domain. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Knowledge MCP server in PolicyLayer and add a rule for content_catalog: 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 Mcp Knowledge. Nothing to install.
content_catalog 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 content_catalog 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 content_catalog. 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.
content_catalog is provided by the Mcp Knowledge MCP server (https://mcp.gapup.io). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Knowledge, and thousands of servers like it.
This server
Across the catalogue