woow_emqx_mcp_server

Overview Schema Source Related Servers Discussions Admin

Enable Or Disable EMQX Rule

emqx_toggle_rule

DestructiveIdempotent

Enable or disable an EMQX rule to control data processing; disabling a rule stops dependent pipelines, so confirm downstream usage first.

Instructions

[DESTRUCTIVE] Switch a rule on or off.

Disabling a rule silently stops whatever pipeline depends on it — confirm which downstream system it feeds before turning it off.

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": {
      "rule_id": "<rule_id>",
      "enable": "<enable>"
    },
    "name": "emqx_toggle_rule"
  }
}

Input Schema

Name	Required	Description	Default
`enable`	Yes	True to switch the rule on, False to switch it off.
`rule_id`	Yes	Rule id to change.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 3, 2026

TDQS

A4.4/5.0

Behavior5/5

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

The description adds significant behavioral information beyond the annotations: it warns that disabling a rule 'silently stops whatever pipeline depends on it' and advises confirming the downstream system. This complements the destructiveHint and readOnlyHint annotations without contradicting them, providing actionable safety context.

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?

The description is extremely concise, containing only two sentences that deliver the core purpose and a critical warning. The '[DESTRUCTIVE]' prefix front-loads the risk, and every sentence earns its place without superfluous detail.

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?

The tool is simple (2 parameters, no nested objects), and the description covers the essential purpose and the key risk. An output schema is available to describe return values, so the description does not need to explain them. It lacks minor details like behavior on nonexistent rule, but overall it is sufficiently complete for a toggle action.

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?

Schema coverage is 100%, with both parameters already well-described in the schema (e.g., 'True to switch the rule on, False to switch it off'). The description does not add additional parameter-level meaning, so the baseline of 3 is appropriate.

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

Purpose5/5

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

The description clearly states the action ('Switch a rule on or off') with a specific verb and resource. It distinguishes from sibling tools like emqx_list_rules and emqx_get_rule_metrics by focusing on enabling/disabling rather than listing or monitoring.

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?

The description provides clear context about when to use the tool (to toggle a rule) and adds a critical caution about disabling rules affecting downstream pipelines. It does not explicitly mention alternatives, but the context is sufficient for an agent to infer the tool's role. A score of 4 reflects clear usage context without explicit when-not guidance.

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