content_taxonomy
Return the enrichment taxonomy of a content domain — every tag grouped by facet (genre, theme, mood, play-mode…). When to use this tool: an agent needs the controlled vocabulary to filter, classify or query content. Input: a domain.
This record as markdown: /tools/io-github-getgapup-gapup-mcp/content-taxonomy.md
What content_taxonomy does on Gapup Mcp
AI agents call content_taxonomy to retrieve information from Gapup Mcp 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 |
|---|---|---|---|
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 |
domain | string | Yes | Content domain |
Parameters from the server's own tool schema.
Why content_taxonomy is rated Low
This tool queries and returns a controlled vocabulary taxonomy for a content domain. It has no side effects, does not modify data, and does not execute arbitrary code or trigger external operations. It is a straightforward data retrieval operation, making it a Read risk category with low severity.
From the tool's definition Tool description states 'Return the enrichment taxonomy' and 'every tag grouped by facet' — purely retrieves structured metadata/vocabulary. Input is a domain parameter; no modification, deletion, or code execution occurs.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs content_taxonomy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gapup Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For content_taxonomy, this is the rule to start with:
content_taxonomy 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 Gapup Mcp, apply this rule, and every content_taxonomy call is checked against it from then on.
Questions about content_taxonomy
Return the enrichment taxonomy of a content domain — every tag grouped by facet (genre, theme, mood, play-mode…). When to use this tool: an agent needs the controlled vocabulary to filter, classify or query content. Input: a domain. It is categorised as a Read tool in the Gapup Mcp MCP Server, which means it retrieves data without modifying state.
content_taxonomy accepts 2 parameters: async, domain. Required: domain. The full parameter table on this page comes from the server's own tool schema.
Register the Gapup MCP server in PolicyLayer and add a rule for content_taxonomy: 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 Gapup Mcp. Nothing to install.
content_taxonomy 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_taxonomy 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_taxonomy. 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_taxonomy is provided by the Gapup MCP server (https://mcp.gapup.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gapup, and thousands of servers like it.
This server
Across the catalogue