Low Risk

browse_wwdc_topics

List all WWDC topic categories with their IDs. Essential first step before using list_wwdc_videos with topic filtering. Returns topic IDs like

How to control browse_wwdc_topics ↓

What browse_wwdc_topics does on Apple Docs MCP

AI agents call browse_wwdc_topics to retrieve information from Apple Docs MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why browse_wwdc_topics needs a policy

This tool only retrieves and enumerates metadata (topic categories and their IDs) from Apple's documentation server. It is a pure query operation with no capability to modify, delete, or execute code. The return of reference IDs for use in subsequent filtering is typical read-only behavior. Severity is low because misuse poses minimal risk—worst case, an agent receives a list of topic categories.

From the tool's definition Tool lists WWDC topic categories and returns topic IDs. The description explicitly states it is a 'first step before using list_wwdc_videos', indicating it retrieves reference data without modifying state. No side effects or write operations are involved.

Documented attack patterns abuse exactly the kind of access browse_wwdc_topics gives an agent:

How to control browse_wwdc_topics

PolicyLayer is an MCP gateway — it sits between your AI agents and Apple Docs MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for browse_wwdc_topics:

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

browse_wwdc_topics is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Apple Docs MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about browse_wwdc_topics

What does the browse_wwdc_topics tool do? +

List all WWDC topic categories with their IDs. Essential first step before using list_wwdc_videos with topic filtering. Returns topic IDs like. It is categorised as a Read tool in the Apple Docs MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on browse_wwdc_topics? +

Register the Apple Docs MCP server in PolicyLayer and add a rule for browse_wwdc_topics: 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 Apple Docs MCP. Nothing to install.

What risk level is browse_wwdc_topics? +

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

Can I rate-limit browse_wwdc_topics? +

Yes. Add a rate_limit block to the browse_wwdc_topics 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 browse_wwdc_topics completely? +

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

browse_wwdc_topics is provided by the Apple Docs MCP server (kimsungwhee/apple-docs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Apple Docs MCP tool call.

Start from Apple Docs MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

18 Apple Docs MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.