mcp-tool-verify

You can verify MCP filesystem tool write operations by enforcing post-call verification, which checks file existence and content through read-back or stat checks to ensure the write operation succeeded and prevent silent failures.

To prevent hallucinated MCP tool parameters, you need parameter validation that checks tool calls against documentation or prior successful usage, ensuring API integrity and blocking non-existent parameters from being executed.

Post-call verification for MCP filesystem tools is the process of confirming that file write operations succeeded by checking file existence and content immediately after the call, needed when silent failures could cause downstream errors.

An MCP file write operation may report success while leaving an empty or missing file due to silent failures, which can be caught by post-call verification that checks file existence and attempts a fallback write if content is missing.

Yes, you can use parameter validation to enforce API discipline for MCP tool calls by validating parameters against documentation or prior successful usage, preventing the execution of non-existent or invented tool parameters.