This is a security proxy, not a functional MCP server. The 5 tools have minimal or missing schemas and descriptions. demo_status has an empty input schema ({}), read_file and run_command lack visible parameter documentation, read_secret and unknown_tool have vague descriptions ('Do something vaguely useful'). No tool descriptions explain WHEN to use them, what they return, or error recovery paths. Schemas are not documented. This server is infrastructure for policy enforcement, not a production tool suite.

• Add complete JSON Schema for each tool's input parameters with type, description, and constraints. demo_status should document any required/optional params; read_file must specify path format and allowed directories.
• Expand descriptions to 50 - 200 characters explaining WHAT the tool does, WHEN to use it, and what it returns. E.g., 'Read a file from the filesystem. Provide the absolute or relative path. Returns file contents as a string. Fails if path is outside allowed directories.'
• Document output schemas for each tool. E.g., read_file returns {content: string, size: number, path: string}. demo_status returns {status: string, timestamp: string}.
• Add error recovery guidance. E.g., 'If run_command fails with exit code 1, check stderr output. Retry with adjusted arguments or call read_file to inspect prerequisites.'
• Rename unknown_tool to a descriptive verb_noun name (e.g., get_system_info, validate_config) and provide a substantive description explaining its purpose.