// MCP TOOL REFERENCE

FEATHERSJS TOOLS

4 tools from the Feathersjs MCP Server, categorised by risk level.

READ TOOLS

search_docs Search the FeathersJS documentation using BGE-M3 dense semantic search. Returns the most relevant documentation chunks for a given query, optionall... 2/5

WRITE TOOLS

submit_documentation Submit a documentation update or new doc as a GitHub Pull Request for admin review. Content is validated locally (schema, path, sanitization, markd... 3/5 update_documentation Update an existing documentation file via a GitHub Pull Request for admin review. The document must already exist in the knowledge base. Content is... 3/5

DESTRUCTIVE TOOLS

remove_documentation Request removal of a documentation file via a GitHub Pull Request for admin review. The document must exist in the knowledge base. If GITHUB_TOKEN ... 5/5

// FAQ

How many tools does the Feathersjs MCP server have? +

The Feathersjs MCP server exposes 4 tools across 3 categories: Read, Write, Destructive.

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

What risk categories do Feathersjs tools fall into? +

Feathersjs tools are categorised as Read (1), Write (2), Destructive (1). Each category has a recommended default policy.

Enforce policies on Feathersjs

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →