7 tools from the Server MCP Server, categorised by risk level.
View the Server policy →aide_info Check whether the host project's AIDE artifacts are up to date. Reads the local .aide/versions.json, compares against the canonical manifest shippe... aide_read Read an .aide spec file with full context. Returns the file content, its classified type (intent/research/plan/todo), related specs in the same dir... aide_validate Health check for .aide spec files in the project. Detects orphaned specs (in folders with no orchestrator), missing specs (orchestrators with 3+ he... 2/5 aide_discover Scan for .aide spec files in this project. Returns a tree map of where specs live, following progressive disclosure.
Without a path: returns a lig... 3/5 aide_scaffold Create new .aide spec files with automatic naming convention enforcement. Handles the naming rules: intent specs are .aide by default, but become i... 3/5 aide_init Bootstrap the AIDE development environment into a project. Returns structured JSON for agent consumption — not prose.
The tool uses a two-call pat... 4/5 aide_upgrade Compare the AIDE methodology artifacts in this project against the canonical versions and return structured JSON results grouped by category. Use t... 4/5 The Server MCP server exposes 7 tools across 3 categories: Read, Write, Execute.
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 Server server.
Server tools are categorised as Read (3), Write (2), Execute (2). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept