Low Risk

content_discovery

Discover content franchises within a domain. Two modes: pass tag for a precise taxonomy match (every game tagged 'co-op'), or pass query for free-text SEMANTIC search powered by pgvector embeddings — finding franchises by meaning ('dark atmospheric games about isolation') even when no literal tag...

Risk signalsAccepts freeform code/query input (query) · Bulk/mass operation — affects multiple targets

Part of the Mcp Knowledge server.

content_discovery is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE MCP KNOWLEDGE →

Free to start. No card required.

AI agents call content_discovery to retrieve information from Mcp Knowledge without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though content_discovery only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "content_discovery": {}
  }
}

See the full Mcp Knowledge policy for all 271 tools.

Get this rule live on your own Mcp Knowledge server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MCP KNOWLEDGE →

View all 271 tools →

These attack patterns abuse exactly the kind of access content_discovery gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so content_discovery only ever does what you allow.

SECURE MCP KNOWLEDGE →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the content_discovery tool do? +

Discover content franchises within a domain. Two modes: pass tag for a precise taxonomy match (every game tagged 'co-op'), or pass query for free-text SEMANTIC search powered by pgvector embeddings — finding franchises by meaning ('dark atmospheric games about isolation') even when no literal tag matches. Results are verifiable: tag mode carries tag confidence/corroboration, semantic mode carries a similarity score; both carry entity freshness. When to use: an agent wants a domain-scoped shortlist by tag or by intent. Inputs: a domain plus either a tag or a free-text query.. It is categorised as a Read tool in the Mcp Knowledge MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on content_discovery? +

Register the Mcp Knowledge MCP server in PolicyLayer and add a rule for content_discovery: 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.

What risk level is content_discovery? +

content_discovery is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit content_discovery? +

Yes. Add a rate_limit block to the content_discovery 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.

How do I block content_discovery completely? +

Set action: deny in the PolicyLayer policy for content_discovery. 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.

What MCP server provides content_discovery? +

content_discovery 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.

Enforce policy on every Mcp Knowledge tool call.

Deterministic rules across all 271 Mcp Knowledge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.