Runtime limits
Limits for MCP tools on Glxymesh: call timeout, memory, message sizes, outbound HTTP, key/value storage, module size and build constraints.
| Limit | Value |
|---|---|
| Time per tool call | 30 seconds, including time spent waiting on outbound HTTP |
| Memory per call | 128 MB |
| Request or response message | 4 MiB |
A call that runs out of time is stopped and returns a timeout error to the client.
Outbound HTTP
Section titled “Outbound HTTP”| Limit | Value |
|---|---|
| Allowed destinations | Hosts in manifest.json egress.allow, and their subdomains |
| Schemes | http, https |
| Timeout per request | 10 seconds |
| Response body | 4 MiB |
Key/value storage
Section titled “Key/value storage”| Limit | Value |
|---|---|
| Key | 512 bytes |
| Value | 1 MiB |
Tools and builds
Section titled “Tools and builds”| Limit | Value |
|---|---|
| Tool name | 1–64 characters: a-z, 0-9, - |
| Published module | 64 MiB |
| Platform build time | 60 seconds |
| Platform build imports | Go standard library, github.com/modelcontextprotocol/go-sdk, glxymesh.com/mcp-core |
| Source layout | One directory; subdirectories aren’t uploaded |
| Languages | Go |
New and updated tools reach the runtime within about 15 seconds of a successful push.
© 2026 Glxymesh