Compare the AIDE methodology artifacts in this project against the canonical versions and return structured JSON results grouped by category. Use this when the user asks to update AIDE, sync AIDE, refresh AIDE, check for AIDE updates, or bring AIDE up to date. This is NOT for editing user .aide s...
Accepts file system path (path); Bulk/mass operation — affects multiple targets
Part of the Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke aide_upgrade to trigger processes or run actions in Server. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
aide_upgrade can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
aide_upgrade:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Server policy for all 7 tools.
Agents calling execute-class tools like aide_upgrade have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
aide_upgrade is one of the high-risk operations in Server. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Compare the AIDE methodology artifacts in this project against the canonical versions and return structured JSON results grouped by category. Use this when the user asks to update AIDE, sync AIDE, refresh AIDE, check for AIDE updates, or bring AIDE up to date. This is NOT for editing user .aide specs — it inspects methodology infrastructure only. The tool uses a two-call pattern for progressive disclosure: **First call (no `category` param):** Returns a lightweight summary — every category with file names, statuses, and counts, but NO file content. Use this to understand what has drifted and present a summary to the user. Ask which categories they want to apply. **Second call (with `category` param):** The tool writes all differs/missing files directly to disk itself and returns a manifest — file results with `filePath`, `status` (`"updated"`, `"created"`, or `"matches"`), and `name`, but NO `canonicalContent`. The agent never sees file content and never uses the Write tool for methodology files. Repeat the second call for each category the user confirms. As the calling agent, you must: 1. Call without `category` first to get the summary 2. Present each drifted category (differs/missing) and ask the user which to apply 3. For each confirmed category, call again with `category=X` — the tool writes the files and returns a manifest. Report what was updated/created to the user. 4. For the `mcp` category, the manifest still includes `prescription` data — merge the entry into the existing MCP config yourself (read → merge → write). If `malformed`, tell the user — do not overwrite. 5. For `ide`, the manifest may include `instructions` for VS Code extension install — execute that command for the user. Zed config is written directly by the tool. **IMPORTANT — one-at-a-time wizard pattern using AskUserQuestion:** Do NOT present all categories at once. Walk the user through ONE category at a time using AskUserQuestion with Yes/Skip options. Stop after each question and wait for confirmation before calling with that category. Categories: pointer-stub, methodology-docs, version-metadata, commands, agents, skills, mcp, ide, readme. Upgrade surface (user code and user .aide specs are never touched): - AIDE pointer stub in the agent config file - Canonical methodology docs under .aide/docs/ - versions.json metadata under .aide/docs/ - Slash commands for all pipeline phases - Pipeline agent files, skill templates - MCP server entry in the project's MCP config - IDE file association config (Zed settings, VS Code extension) Supports Claude Code, Cursor, Windsurf, and Copilot. Auto-detects the framework or accepts an override.. It is categorised as a Execute tool in the Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for aide_upgrade. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Server MCP server.
aide_upgrade is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the aide_upgrade rule in your Intercept policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the Intercept policy for aide_upgrade. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
aide_upgrade is provided by the Server MCP server (@aidemd-mcp/server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept