Agent Decoy Gateway
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| port | No | Port for the combined REST/MCP HTTP server (`agent-decoy combined --port 8765`). REST routes are served on http://127.0.0.1:<port>/v1/* and the MCP Streamable HTTP endpoint at http://127.0.0.1:<port>/mcp. Only loopback binding is accepted. | 8765 |
| denial-policy | No | Denial policy for the combined server (`--denial-policy deny|decoy`). The default `deny` denies invalid-grant transfers directly; the opt-in lab-only `decoy` returns `verification_required` plus a bounded reference instead, while still committing no transfer. | deny |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookup_settlement_referenceC | Open a synthetic settlement-reference trail in an isolated security lab. |
| follow_settlement_referenceC | Follow one synthetic reference handle; the trail has a hard step limit. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct roles: one opens/creates a synthetic settlement-reference trail, while the other follows an existing reference handle. The descriptions make the sequence and action boundaries explicit, so an agent should not confuse them.
Both names follow a consistent verb_noun pattern: lookup_settlement_reference and follow_settlement_reference. The shared object name reinforces the relationship without creating naming ambiguity.
Two tools is thin for a gateway surface, even if the intended workflow is deliberately minimal. The set is not bloated, but it sits at the borderline where more lifecycle operations may be expected.
The basic open-and-follow workflow is covered, but there is no visible way to list trails, inspect status, close/reset a trail, or handle errors beyond the hard step limit. These are notable gaps for a stateful reference-trail domain, though agents may work around them.