Schema | sandbox

sandbox

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

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.

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`	{}

Functions exposed to the LLM to take actions

Name	Description
run_privilegedA	Request a privileged shell command. A human approves; you get the output. The command runs OUTSIDE the sandbox on your behalf — you never receive root yourself. Returns the captured stdout/stderr on approval.
request_path_accessA	Request a file operation OUTSIDE the sandbox folder. A human approves; the sandbox performs the read or write on your behalf (you never receive the capability). mode is "read" or "write"; for "write", pass the file content in `content`.
fetch_urlA	Fetch a URL through the sandbox. A human approves; you get the body. Network access is gated — the sandbox performs the fetch outside your context so you never make the request directly.
check_requestA	Retrieve the outcome of an escalation (from MCP OR the hook). Use this after run_privileged returns 'pending', or to pick up a request the Claude Code hook raised.
sandbox_statusA	Show the sandbox root, triggers, and any pending escalations.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Boredem125/architecture-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server