Universal Poison Armor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sanitize_documentA | Sanitize an incoming untrusted text document, file content, user input, or RAG retrieval chunk against AI poisoning. Strips Markdown XSS tracking pixels, neutralizes hidden zero-width Unicode steganography, redacts prompt injection phrases, and replaces high-entropy mathematical adversarial suffixes (GCG attacks). Usage Guidelines:
Behavior & Side Effects:
|
| scan_dataset_for_anomaliesA | Scan a collection of documents, training examples, or retrieved RAG items for semantic anomalies and poisoned clusters. Uses dense sentence embeddings ( Usage Guidelines:
Behavior & Side Effects:
|
| verify_article_consensusA | Verify web search results or news articles to defend against Consensus Poisoning and Sybil attacks. Audits domain Top-Level Domains (validating trusted authorities like .gov, .edu) and calculates pairwise semantic cosine similarities to detect coordinated flooding campaigns where multiple untrusted sources syndicate near-identical (similarity > 0.95) fake consensus. Usage Guidelines:
Behavior & Side Effects:
|
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 3 tools
Each tool targets a clearly distinct attack surface: single-document sanitization, dataset-level anomaly detection, and multi-source consensus verification. The descriptions include explicit WHEN NOT TO USE cross-references that direct the agent to the correct sibling tool, leaving no ambiguity.
All three tool names follow the same snake_case verb_noun pattern: sanitize_document, scan_dataset_for_anomalies, and verify_article_consensus. The verbs are specific and accurately describe each tool's core action.
Three tools is well-scoped for this specialized defensive server, with one tool covering each major poisoning vector: input text, training/retrieval datasets, and web-sourced consensus claims. Every tool earns its place, and there are no redundant or filler tools.
The tool set covers the core defense workflow: sanitize untrusted input, detect poisoned clusters in datasets, and verify whether apparent consensus is authentic. A minor gap is the lack of a dedicated tool for reading or querying the security_audit.json log that all tools append to, but this is workable via external file access.