file_type_detect
Identify what a file really is from its bytes (not its name): 80+ signatures (images, audio, video, archives, PDF / Office / OpenDocument / EPUB, executables ELF / PE / Mach-O / WASM, fonts, SQLite / Parquet / pcap, ML model files GGUF / safetensors / PyTorch / pickle), container sniffing (DOCX v...
This record as markdown: /tools/com-it-scorptech-x402/file-type-detect.md
What file_type_detect does on ScorpTech x402 API
AI agents use file_type_detect to create or update resources in ScorpTech x402 API, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ScorpTech x402 API environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | — | Public URL (only the first 64 KB is read) |
data | string | — | File content, base64 (standard or URL-safe; data: URI accepted) |
filename | string | — | Declared file name, checked against the content |
mimeType | string | — | Declared MIME type, checked against the content |
Parameters from the server's own tool schema.
Why file_type_detect is rated Medium
An AI agent can call file_type_detect faster than any human can review: one bad instruction and it creates or modifies resources in ScorpTech x402 API by the hundred, each call as confident as the last.
Risk signalsAccepts file system path (filename) · Accepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs file_type_detect safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For file_type_detect, this is the rule to start with:
file_type_detect stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every file_type_detect call is checked against it from then on.
Questions about file_type_detect
Identify what a file really is from its bytes (not its name): 80+ signatures (images, audio, video, archives, PDF / Office / OpenDocument / EPUB, executables ELF / PE / Mach-O / WASM, fonts, SQLite / Parquet / pcap, ML model files GGUF / safetensors / PyTorch / pickle), container sniffing (DOCX vs XLSX vs JAR vs APK, tar.gz, MP4 vs HEIC vs AVIF, WebP / WAV / AVI), text sniffing (JSON, XML, SVG, HTML, CSV, PEM, scripts) and image dimensions. Flags risky content (executables, macros, pickles, shortcuts) and mismatches with the declared file name or MIME type. Base64 input (up to ~140 KB) or a URL (first 64 KB, SSRF-safe). Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/file-type-detect. It is categorised as a Write tool in the ScorpTech x402 API MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
file_type_detect accepts 4 parameters: url, data, filename, mimeType. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for file_type_detect: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches ScorpTech x402 API. Nothing to install.
file_type_detect is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the file_type_detect rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for file_type_detect. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
file_type_detect is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue