6 tools from the Mcp File Processor MCP Server, categorised by risk level.
View the Mcp File Processor policy →chunk_text Split text into overlapping chunks suitable for RAG/embedding pipelines. Configurable chunk size and overlap. Returns chunks with positional metadata. detect_language Detect whether content is code, natural language, or mixed. Optionally detects the programming language from file extension. Useful for routing con... 2/5 extract_keywords Extract ranked keywords from text. Returns keywords sorted by frequency, useful for tagging, search indexing, and topic identification. extract_text Extract text content from a file. Supports PDF, DOCX, CSV, JSON, Markdown, HTML, and code files. Pass file content as base64 (for binary formats li... process_file All-in-one file processing: extract text, detect content type, extract keywords, and chunk for RAG. Returns the complete processed result in a sing... server_info Returns server metadata: name, version, registered tools, and registered resources. Useful for introspection and health checks. The Mcp File Processor MCP server exposes 6 tools across 1 categories: Read.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Mcp File Processor server.
Mcp File Processor tools are categorised as Read (6). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept