Microgram: comms-security-gate
Validates communication security posture before transmitting. Gates on mTLS status, firmware signature, replay protection, and encryption. Blocks transmission if security requirements unmet for the link type.
Taxonomy
Linnaean classification joined from the algovigilance taxonomy index via the parent config's rank.
| Rank | Value |
|---|---|
| domain | Substrata |
| kingdom | Constructa |
| phylum | Configa |
| class | station-config |
| order | algovigilance |
| family | mcp-tool-config |
Characteristics:
- substrate:
config - domain:
pv - lifecycle:
continuous - authority:
read - compounding:
producer - io:
agent-request→tool-response
Input schema
link_typestringrequired — Input variable link_typemtls_activeboolean — Whether mTLS handshake is establishedfirmware_signedboolean — Whether modem/radio firmware signature verified at bootreplay_nonce_validboolean — Whether replay protection nonce counter is currentcertificate_pinnedboolean — Whether TLS certificate is pinned to known CA
Example call
POST /api/mcp
Content-Type: application/json
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "station__algovigilance__microgram-comms-security-gate",
"arguments": {
"link_type": ""
}
}
}How to invoke from a client
From any MCP-aware client, add https://algovigilance.com/api/mcp as an MCP server, then call this tool by name. From a raw HTTP client, send the JSON-RPC body above to /api/mcp.
Agent-friendly formats
Working inside an AI assistant? Use the Copy for AI button at the top of this page (or view the raw Markdown) to paste a clean, token-budgeted version of this tool's contract into your conversation.
Related
- All tools (7718 live)
- /api/mcp — endpoint
- /AGENTS.md — agent guide
- /tools/algovigilance__microgram-comms-security-gate/raw.md — this page's Markdown twin