xcodebuildmcp-tool-contract-review

Validate XcodeBuildMCP tool contracts by applying guardrails during reviews to ensure manifest ids match filenames, module paths point to correct implementations, and tool exports include both schema and handler.

A tool contract audit checks MCP manifests and workflows to ensure tool exports declare required schemas and handlers, modules point to correct implementation paths, and tool names remain globally unique across the runtime environment.

Ensure MCP tool names remain globally unique by running review passes across src/mcp/tools, manifests, and runtime schemas to enforce naming consistency and identify duplicate declarations during guardrail audits.

Yes, you can use guardrail reviews to secure XcodeBuildMCP workflow exposure by validating runtime schemas and implementation paths to prevent security gaps and ensure consistent behavior across all exposed tool workflows.

MCP tool manifest validation fails when manifest ids do not match filenames, module paths include file extensions, or tool exports lack required schema and handler declarations across the implementation files.