Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
manifestNoPath to the Lure bait manifest (passed as `--manifest`, e.g. `python3 -m lure mcp --manifest /path/to/baits/manifest.json`). The server reads the manifest and the alert log that `lure listen` writes.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Lure plants fake credentials and reports when an attacker uses one. Start with lure_status. A high alert means someone found and tried a bait.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
lure_statusA

Summary of the bait set: how many baits, which have been used, open alerts, and the attacker's path per source address.

lure_alertsB

Recent alerts, newest first. Use this to answer 'has anyone used a bait?'.

lure_baitsA

Every live bait: file, username, service, where it is meant to be planted, where it was recorded as planted, and whether it has been triggered. Passwords are never returned.

lure_generateB

Write a fresh bait set into the manifest's folder. Only use this for a new deployment; to replace an existing set use lure_rotate.

lure_recordB

Record where a bait was actually planted, so alerts name the exact place.

lure_rotateB

Replace the baits with fresh ones. Old baits stay in the manifest as retired and still alert.

lure_acknowledgeB

Mark an alert as investigated by its id (from lure_alerts).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a distinct role: status summarizes, alerts lists events, baits lists inventory, generate creates a new set, record logs placement, rotate replaces baits, and acknowledge handles alerts. The generate-versus-rotate boundary is explicitly clarified, and the read tools differ by resource shape rather than duplicating behavior.

Naming Consistency4/5

All tools share the `lure_` prefix and snake_case formatting, which is highly predictable. However, read tools use noun-style names (`status`, `alerts`, `baits`) while action tools use verbs (`generate`, `record`, `rotate`, `acknowledge`), so it is not a strict verb_noun convention throughout.

Tool Count5/5

Seven tools is well-scoped for a bait/honeytoken management server. Each tool covers a distinct lifecycle step, and there are no redundant or filler tools.

Completeness4/5

The surface covers the core lifecycle: generating baits, recording placements, rotating them, viewing status/inventory, receiving alerts, and acknowledging alerts. Minor gaps exist, such as no dedicated alert-detail retrieval or per-bait custom creation/removal, but the main workflows are covered.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues