MCP Action Firewall
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Activates per-server rules from your config. Without it, only global rules apply. | |
| config | No | Custom config file path. Without it, uses firewall_config.json in your current directory, or the bundled defaults. | |
| target | Yes | The full command to launch the real MCP server. This is the server you want to protect (e.g., 'npx @modelcontextprotocol/server-github'). | |
| verbose | No | Turns on debug logging (written to stderr, won't interfere with MCP traffic). |
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
}
}
} |
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": true,
"listChanged": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| echoB | Echoes back the input string |
| get-annotated-messageC | Demonstrates how annotations can be used to provide metadata about content. |
| get-envA | Returns all environment variables, helpful for debugging MCP server configuration |
| get-resource-linksC | Returns up to ten resource links that reference different types of resources |
| get-resource-referenceC | Returns a resource reference that can be used by MCP clients |
| get-structured-contentB | Returns structured content along with an output schema for client data validation |
| get-sumB | Returns the sum of two numbers |
| get-tiny-imageA | Returns a tiny MCP logo image. |
| gzip-file-as-resourceA | Compresses a single file using gzip compression. Depending upon the selected output type, returns either the compressed data as a gzipped resource or a resource link, allowing it to be downloaded in a subsequent request during the current session. |
| toggle-simulated-loggingB | Toggles simulated, random-leveled logging on or off. |
| toggle-subscriber-updatesA | Toggles simulated resource subscription updates on or off. |
| trigger-long-running-operationC | Demonstrates a long running operation with progress updates. |
| simulate-research-queryA | Simulates a deep research operation that gathers, analyzes, and synthesizes information. Demonstrates MCP task-based operations with progress through multiple stages. If 'ambiguous' is true and client supports elicitation, sends an elicitation request for clarification. |
| firewall_confirmB | Call this tool ONLY when the user provides the correct 4-digit approval code to confirm a paused action. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| simple-prompt | A prompt with no arguments |
| args-prompt | A prompt with two arguments, one required and one optional |
| completable-prompt | First argument choice narrows values for second argument. |
| resource-prompt | A prompt that includes an embedded resource reference |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| architecture.md | Static document file exposed from /docs: architecture.md |
| extension.md | Static document file exposed from /docs: extension.md |
| features.md | Static document file exposed from /docs: features.md |
| how-it-works.md | Static document file exposed from /docs: how-it-works.md |
| instructions.md | Static document file exposed from /docs: instructions.md |
| startup.md | Static document file exposed from /docs: startup.md |
| structure.md | Static document file exposed from /docs: structure.md |
TDQS
Scored across 14 tools
Most tools have clearly distinct purposes, but some get-* tools like get-annotated-message and get-structured-content could be confused, and get-resource-links vs get-resource-reference are similar.
Tool names mix hyphens (get-env) and underscores (firewall_confirm), and verbs vary inconsistently (echo, get-, toggle-, simulate-, trigger-, gzip-), lacking a uniform pattern.
14 tools is a reasonable count, but the server name implies a firewall/pause/confirm focus, while most tools are demo utilities, creating a scope mismatch.
The server name suggests a firewall use case, but only one tool (firewall_confirm) supports that; the remaining tools are unrelated demos, leaving a significant gap between promise and functionality.