// MCP TOOL REFERENCE

DEV TOOLS

7 tools from the Dev MCP Server, categorised by risk level.

READ TOOLS

get_file_info Get detailed information about a file or directory (size, permissions, timestamps, etc.) 2/5 list_directory List files and directories in a specified path 2/5 read_text_file Read a text file from the filesystem. Returns the file content as text. 2/5 search_files Recursively search for files and directories matching a pattern 2/5

WRITE TOOLS

create_directory Create a directory. Creates parent directories if they don't exist. 3/5 move_file Move or rename a file or directory 3/5 write_file Write content to a file. Creates the file if it doesn't exist, overwrites if it does. 3/5

// FAQ

How many tools does the Dev MCP server have? +

The Dev MCP server exposes 7 tools across 2 categories: Read, Write.

How do I enforce policies on Dev tools? +

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 Dev server.

What risk categories do Dev tools fall into? +

Dev tools are categorised as Read (4), Write (3). Each category has a recommended default policy.

Enforce policies on Dev

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →