tie-mcp-server

export_attacks

Export attacks as CSV rows using specified profile, resource type, and value. Supports filtering by date, search, attack type, and order.

Instructions

Get all attacks in CSV rows format Note: profileId selects a configuration profile (a lens, not a container). If the user has not specified a profile, call get_preferred_profile (or get_preferences) and use preferredProfileId — do not assume profile 1.

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": {
      "profileId": "<profileId>",
      "resourceType": "<resourceType>",
      "resourceValue": "<resourceValue>"
    },
    "name": "export_attacks"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Query parameter: limit
`order`	No	Query parameter: order
`search`	No	Query parameter: search
`dateEnd`	No	Query parameter: dateEnd
`dateStart`	No	Query parameter: dateStart
`profileId`	Yes	Path parameter: profileId
`resourceType`	Yes	Query parameter: resourceType
`attackTypeIds`	No	Query parameter: attackTypeIds
`includeClosed`	No	Query parameter: includeClosed
`resourceValue`	Yes	Query parameter: resourceValue

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 6, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description must cover behavioral traits. It mentions CSV format and clarifies profileId meaning, but does not disclose whether the operation is read-only, rate limits, or potential large data handling. The guidance on profileId is helpful but incomplete for full transparency.

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 short and to the point, but the first sentence lacks proper punctuation before 'Note'. The guidance is front-loaded. It earns a 4 for efficiency despite minor formatting issues.

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?

Given 10 parameters, no output schema, and no annotations, the description should provide more details. It explains profileId and usage, but does not describe the return format (inline CSV vs file), or how filter parameters like resourceType affect the output. The note is helpful, but overall completeness is average.

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

Parameters4/5

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

Schema description coverage is 100%, but generic. The description adds important context for profileId (lens vs container). However, other parameters like resourceType and resourceValue lack explanation beyond their enum/type. The extra context for profileId justifies a 4.

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?

The description clearly states the tool exports attacks in CSV format, distinguishing it from likely JSON-returning sibling 'list_attacks'. However, it could be more explicit about the filtering parameters.

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

Usage Guidelines5/5

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

Provides explicit guidance on how to obtain the profileId by calling 'get_preferred_profile' or 'get_preferences', and warns against assuming profile 1. This is a clear when-to-use instruction.

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

Deploy Server