Skip to main content
Glama
solomonneas

rapid7-mcp

by solomonneas

add_threat_indicator

Add an indicator of compromise (IOC) such as IP, domain, or hash to the InsightIDR custom threat library for improved threat detection.

Instructions

Add a new IOC (IP, domain, hash, etc.) to the InsightIDR custom threat library

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoTags for categorization
typeYesType of indicator
valueYesIndicator value (e.g., '10.0.0.1', 'malware.example.com', SHA256 hash)
severityNoSeverity level of the threatMEDIUM
confidenceNoConfidence score (0-100)
descriptionNoDescription of why this indicator is malicious
threat_nameNoAssociated threat name or campaign
Behavior2/5

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

No annotations provided, so description must cover behavioral traits. It only says 'Add a new IOC' but doesn't specify idempotency, duplicate handling, authorization needs, or side effects. Missing important context for a mutation tool.

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

Conciseness4/5

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

The description is a single concise sentence that is front-loaded. However, it could include additional important details without becoming overly long.

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

Completeness2/5

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

For a tool with 7 parameters and no output schema or annotations, the description is too sparse. It lacks information about return values, error handling, and behavioral constraints, making it incomplete.

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%, so parameters are well-documented in the schema. The description adds minimal extra meaning beyond mentioning IOC types. Baseline is 3, and description does not exceed it.

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 'Add a new IOC' with a specific verb and resource, and gives examples of IOC types (IP, domain, hash). It distinguishes from sibling tools like list_threat_indicators.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus others. No mention of prerequisites, context, or when not to use it. The description just states the basic action.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/solomonneas/rapid7-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server