{"version":"2.1.223","anchor":"remote-agent-and-mcp-task-metadata-files-are-schema-validate","canonical_anchor":"remote-agent-and-mcp-task-metadata-files-are-schema-validate","heading":"Remote agent and MCP task metadata files are schema-validated","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/remote-agent-and-mcp-task-metadata-files-are-schema-validate","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Remote agent and MCP task metadata files are schema-validated\n\nMalformed remote agent and MCP task metadata files are now skipped rather than trusted.\n\n**What**\n\nSidecar `.meta.json` files are now parsed through a zod schema before their contents are used.\n\n**Details**\n\n- `listRemoteAgentMetadata` runs `safeParse` on each file and skips invalid ones, logging the parse error\n- both the sync and async MCP task listers do the same, so arbitrary JSON no longer flows into the list\n\n**Evidence**\n\n`listMcpTaskMetadata: skipping `, `listRemoteAgentMetadata: skipping `\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}