arc-gate-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POLICY | No | Policy mode: balanced, browser_agent, finance_agent, rag_assistant, or strict | balanced |
| UPSTREAM | Yes | The upstream MCP server command (e.g., 'uvx mcp-server-fetch') |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetchA | Calls the 'fetch' tool on the upstream MCP server. Pass arguments as keyword arguments matching the upstream tool's input schema. For the fetch tool: url (required, string) is the URL to retrieve; max_length (optional, int) limits response size; raw (optional, bool) returns HTML instead of markdown. Arc Gate inspects all results for prompt injection before they reach your agent. Policy: balanced. No authentication required. Blocked results return an error string. |
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 1 tool
Only one tool exists, so there is no possibility of ambiguity.
The single tool is named 'fetch', following a clear verb-based naming convention.
One tool is entirely appropriate for a server designed as a secure proxy for the fetch operation.
The server fully covers its stated purpose of fetching URLs with security inspection; no additional tools are needed.