Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Set Ioc Monitoring

set_ioc_monitoring
Destructive

Toggle monitoring for specific Indicators of Compromise in file-level malware detection, enabling or disabling entries and requiring server confirmation when detection is weakened.

Instructions

Enable or disable monitoring of specific Indicators of Compromise (IoC) in file-level malware detection.

indicators names the IoC entries to switch (as listed by api_read('/api/v1/malwareDetection/settings/fileDetection/indicatorsOfCompromise') or the VBR console). Disabling weakens detection and is confirmed by the server.

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": {
      "enabled": "<enabled>",
      "indicators": "<indicators>"
    },
    "name": "set_ioc_monitoring"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYes
indicatorsYes
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, so the safety profile is covered. The description adds genuine context beyond that: disabling weakens detection and the server confirms the change. It still does not explain the confirmation mechanism or what state is left behind, so it adds value but is not rich.

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 paragraphs, front-loaded with the action, followed by the parameter hint and the risk warning. Every sentence carries information; there is no filler or repetition of the schema.

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

Completeness3/5

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

An output schema exists, so return values need not be described, and annotations cover the destructive profile. However, for a destructive mutation with a required confirm_token workflow, the description never explains how confirmation is obtained or when the token is needed, which is the main thing an agent could get wrong.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry all parameter meaning. It documents `indicators` well, including how to enumerate valid entries, but says nothing about `enabled` beyond the verb, and nothing at all about `confirm_token`, which is the least self-explanatory parameter. With only one of three parameters addressed, it doesn't compensate for the coverage gap.

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 pair (enable/disable) plus the exact resource: IoC entries within file-level malware detection. It is clearly scoped and not a tautology of the title. It stops short of differentiating itself from the related sibling set_backup_file_malware_state, which operates in the same malware-state area.

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?

It gives real operational context: the indicator names come from a named api_read endpoint or the VBR console, and it warns that disabling weakens detection. There is no explicit when-not guidance or comparison to a sibling tool, so it stops at clear context rather than full routing guidance.

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