// MCP TOOL REFERENCE

PROJECTS EMMANUEL TOOLS

10 tools from the Projects Emmanuel MCP Server, categorised by risk level.

READ TOOLS

getProjectById Retrieves a single project by its unique identifier. getTaskById Retrieves a single task by its unique identifier within a project. listProjects Retrieves a paginated list of all projects. listTasksForProject Retrieves a paginated list of tasks for a specific project.

WRITE TOOLS

createProject Creates a new project resource. 2/5 createTask Creates a new task within a specified project. 2/5 updateProject Updates an existing project by its unique identifier. 2/5 updateTask Updates an existing task by its unique identifier. 2/5

DESTRUCTIVE TOOLS

deleteProject Deletes a project by its unique identifier. This action is irreversible. 4/5 deleteTask Deletes a task by its unique identifier. This action is irreversible. 4/5

// FAQ

How many tools does the Projects Emmanuel MCP server have? +

The Projects Emmanuel MCP server exposes 10 tools across 3 categories: Read, Write, Destructive.

How do I enforce policies on Projects Emmanuel 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 Projects Emmanuel server.

What risk categories do Projects Emmanuel tools fall into? +

Projects Emmanuel tools are categorised as Read (4), Write (4), Destructive (2). Each category has a recommended default policy.

Enforce policies on Projects Emmanuel

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →