zeek-mcp

Overview Schema Source Related Servers Discussions Admin

zeek_executable_downloads

Identify executable file transfers (PE, ELF, Mach-O binaries and scripts) on the network to detect potential malware delivery within a specified time range.

Instructions

Find executable file transfers on the network - PE, ELF, Mach-O binaries and scripts that may indicate malware delivery.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

Name	Required	Description	Default
`timeTo`	No	End time (ISO 8601)
`timeFrom`	No	Start time (ISO 8601)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.0.0Jul 14, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. Fails to disclose read-only nature, required permissions, result format, or any filtering beyond time range. Minimal behavioral context.

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?

Single sentence, no redundancy, front-loaded with verb and resource. Efficient but could include more information without becoming verbose.

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 no output schema and simple parameters, description is minimal but lacks details on return values, pagination, or aggregation. Adequate but not comprehensive.

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 for both parameters is 100% with clear ISO 8601 descriptions. Description adds no additional meaning beyond schema, meeting baseline for high coverage.

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?

Description clearly states verb 'Find' and resource 'executable file transfers on the network', listing specific binary types (PE, ELF, Mach-O) and hinting at malware delivery context. This distinguishes it from sibling tools like zeek_query_files or zeek_suspicious_http.

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 alternatives. Lacks prerequisites, exclusions, or comparison to siblings. Usage is merely implied by the description.

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