aide_discover

// WHEN AI AGENTS USE THIS TOOL

AI agents use aide_discover to create or modify resources in Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON AIDE_DISCOVER

Without a policy, an AI agent could call aide_discover repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Server.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

io-github-aidemd-mcp-server.yaml

tools:
  aide_discover:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Server policy for all 7 tools.

// DETAILS

Tool Name aide_discover

Category Write

MCP Server Server MCP Server

Risk Level Medium

// MORE SERVER TOOLS

Execute aide_init Execute aide_upgrade Write aide_scaffold Read aide_info Read aide_read Read aide_validate

// WHAT CAN GO WRONG

Agents calling write-class tools like aide_discover have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER WRITE TOOLS ACROSS MCP SERVERS

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

AbraFlexi contact_create AbraFlexi contact_update AbraFlexi evidence_create AbraFlexi evidence_update AbraFlexi invoice_issued_update AbraFlexi invoice_received_create

// RELATED READING

// FAQ

What does the aide_discover tool do? +

Scan for .aide spec files in this project. Returns a tree map of where specs live, following progressive disclosure. Without a path: returns a lightweight project-wide map — file locations and types only, no content. Use this once to understand the project's spec architecture. With a path: the response opens with the ancestor chain — the cascading intent lineage from project root down to the target directory, with each ancestor showing its description and alignment status (aligned/misaligned when set). The ancestor chain gives you the full inherited context before you read a single spec body. After the ancestor chain comes the detailed subtree of the target directory — summaries extracted from file content and anomaly warnings. Use this to drill into the area you're working on. .aide files are progressive disclosure specs that live next to orchestrator code — they contain intent (strategy, implementation contracts, anti-patterns), research (sources, data, patterns), or QA checklists (todo). Read .aide files BEFORE reading code — they are the context layer between folder structure and implementation details. File types (.aide, intent.aide, research.aide, plan.aide, todo.aide): - .aide — Intent spec (default). Strategy, contracts, anti-patterns. - intent.aide — Same as .aide, used only when research.aide exists in the same folder. - research.aide — Raw research. Sources, data points, pattern synthesis. - plan.aide -- Architect's implementation plan. Checkboxed steps for the implementor. - todo.aide — QA re-alignment document. Captures where implementation drifted from intent. Never have both .aide and intent.aide in the same folder.. It is categorised as a Write tool in the Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on aide_discover? +

Add a rule in your Intercept YAML policy under the tools section for aide_discover. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Server MCP server.

What risk level is aide_discover? +

aide_discover is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit aide_discover? +

Yes. Add a rate_limit block to the aide_discover 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.

How do I block aide_discover completely? +

Set action: deny in the Intercept policy for aide_discover. 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.

What MCP server provides aide_discover? +

aide_discover 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.

Enforce policies on Server