No generic executor or operation dispatcher
OpenAI does not allow discovery, operation selection or schema fetching with a generic executor that enables operations not individually exposed for review; expose each operation as its own tool.
Check openai-generic-executor · OpenAI plugin directory · default severity: blocking · rubric 2.1.0
What fails
A tool that runs an operation, tool or command named in an argument hides those operations from review and from the hints.
The rule
Do not use discovery, operation selection, or schema fetching with a generic executor to enable operations not individually exposed for review.
How to fix it
Expose each operation as its own tool with its own schema and annotations.
- Replace execute(operation, params) with one tool per operation.
- Give each its own inputSchema and annotations.
- If the catalog is large, group by resource rather than hiding operations behind one tool.
TypeScript SDK
import { McpServer } from '@modelcontextprotocol/server';
import * as z from 'zod';
const server = new McpServer({ name: 'issues', version: '1.0.0' });
server.registerTool(
'archive_project',
{
title: 'Archive project',
description: 'Archive one project; it can be restored later. Use when the user asks to archive or shelve a project.',
inputSchema: z.strictObject({
project_id: z.string().describe('Project ID, for example PRJ-7'),
}),
annotations: { readOnlyHint: false, destructiveHint: true, openWorldHint: false },
},
async ({ project_id }) => ({ content: [{ type: 'text', text: 'Done' }] }),
);Python SDK
from typing import Annotated
from pydantic import Field
from mcp.server.mcpserver import MCPServer
from mcp.types import ToolAnnotations
server = MCPServer("issues")
@server.tool(
title="Archive project",
annotations=ToolAnnotations(readOnlyHint=False, destructiveHint=True, openWorldHint=False),
)
def archive_project(
project_id: Annotated[str, Field(description="Project ID, for example PRJ-7")],
) -> str:
"""Archive one project; it can be restored later. Use when the user asks to archive or shelve a project."""
return "Done"Run against @modelcontextprotocol/server 2.4.0, mcp 2.3.0 and fastmcp 4.2.2 on 2026-11-18; the checker confirms this check passes on the tool list each snippet produces.
Questions
Our API has 300 operations. Do we need 300 tools?
Expose the operations the app needs, each as a tool. Reviewers must be able to see and judge each operation and its annotations; a dispatcher hides them.
Is a search tool that returns tool names a problem?
Discovery alone is fine if every operation it points to is itself an exposed, annotated tool. The rule targets running unexposed operations.
Related checks
- Reads and writes are separate tools
- Custom query tools name or link the target API
- No steering of when other tools are used
- All checks in Directory review rules for MCP tools
How this check is graded
It counts toward: OpenAI plugin directory. See the rubric.
Last verified against OpenAI plugin guidelines, section 6.2 on 2026-11-18. The rule above is quoted in the source’s own words. This page as Markdown.
Check your tool list: paste your tools/list, nothing is sent anywhere