Chainsaw MCP Server

by MadameFabulous

Overview Schema Source Related Servers Discussions Admin

Python

Local

Chainsaw: delete custom rule

chainsaw_delete_rule

DestructiveIdempotent

Delete a custom detection rule by name. Bundled Chainsaw and Sigma rules are protected and cannot be removed.

Instructions

Delete a custom rule. Bundled Chainsaw and Sigma rules cannot be deleted.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "chainsaw_delete_rule"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Custom rule file name.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 27, 2026

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds a real operational constraint (bundled Chainsaw/Sigma rules are protected) that prevents a predictable failure, though it does not state permanence or the error behavior when the name is invalid.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with zero filler; the action is front-loaded and the constraint follows immediately. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter destructive delete with full annotation coverage and no output schema, the definition is essentially complete. The only minor gap is what a successful deletion returns and whether it is permanent, which the agent could reasonably infer from the destructive/idempotent hints.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter with 100% schema description coverage, so the schema already documents it as the custom rule file name. The description adds no syntax, format, or matching semantics (e.g., name vs. file path), so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (delete) and resource (custom rule), clearly separating it from the other rule-related siblings (get_rule, save_rule, search_rules) and from result deletion. It stops short of any sibling-by-name routing, but the operation is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides an explicit negative condition: bundled Chainsaw and Sigma rules cannot be deleted, which tells the agent when this tool will fail. There is no positive when-to-use framing beyond the obvious, so it falls short of the 5-level 'explicit when/when-not/alternatives' standard.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.