LLPROBeta

Home / Businesses / Path Length and Illegal Character Check

Path Length and Illegal Character Check

Check Windows paths before a copy, sync or unzip: length against the 260 limit, names over 255, illegal characters, reserved names like CON and NUL, trailing dots, each by part, signed; paths are not echoed.

Testing

What it does
Check Windows paths before a copy, sync or unzip: length against the 260 limit, names over 255, illegal characters, reserved names like CON and NUL, trailing dots, each by part, signed; paths are not echoed.
Who it is for
Businesses.
Start in one step
Ask your agent to call path_length_check at llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it.
What to expect
Testing: open to try. Free

New to this? Start here.

What it does

Path Length and Illegal Character Check is for agents that move or sync files for a business (cloud drive to Windows PCs, archives, migrations) and need to catch paths Windows will refuse or silently change before the job fails half way. Check Windows file and folder paths before copying, syncing or unzipping files. Send up to 100 paths; get back per path the length (in the UTF-16 units Windows counts) against the 260 MAX_PATH limit (259 characters for a file, 247 for a folder, about 32,767 with long paths or \\?\), names over 255 characters, illegal characters (< > : " | ? * and control characters), reserved names (CON, PRN, AUX, NUL, COM1-9, LPT1-9, also with an extension like NUL.txt) and names ending in a space or a period, each by part number. Paths are not echoed back. It is one of the Files and records department tools LLPRO builds for the work agents do across business software (Google Drive, Dropbox, OneDrive, Box). Every answer carries the written rule it used, what it does not do, its sources with dates, and an Ed25519 signature you can check against the key below.

Who it is for
Agents that move or sync files for a business (cloud drive to Windows PCs, archives, migrations) and need to catch paths Windows will refuse or silently change before the job fails half way.
Price
Free, no sign-up: 120 calls an hour per address and 3,000 an hour across all callers. Paid calls are planned and not charging.
Limits
Up to 30,000 bytes per call, paths up to 100 entries; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Nothing you send is stored by the tool; no model and no network are used. Does not look at a disk, so it cannot tell whether a path exists, what the current folder adds to a relative path, or the real limit of a given file system (some network shares and older systems differ). Does not check Linux or macOS rules beyond what Windows forbids, the 8.3 short names, or permissions. Windows 11 relaxes some reserved-name cases in some programs; the documented rule is applied. Paths are not echoed or stored.

For developers: try it

POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "path_length_check", "arguments": {"paths": ["C:\\Users\\Public\\report.txt"]}}}

For agents

Tool path_length_check on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:zte4frye67gwz7l5yji5hjk7mu): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).

Public key (base64): JcCn444c2H0nggylA6BylYCs1fBxCkzN7zP5zqlkP68=

For agents that search MCP registries for path length, MAX_PATH, 260 character limit tools (listed in MCP registries, served by the LLPRO gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.

Next

For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card