boltzgen_submit
AI agents invoke boltzgen_submit to trigger actions in BoltzGen MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool name 'boltzgen_submit' strongly implies submitting a job for execution on the GPU-accelerated Docker infrastructure. In the context of this server (which runs computationally intensive protein design jobs), submitting a job triggers external computation.
From the tool's definition Tool name 'boltzgen_submit' on a server that runs GPU-accelerated Docker jobs for protein design; sibling tool 'boltzgen_run' and async job management context imply job submission/execution.
Attacks that exploit this kind of access
boltzgen_submit. It is categorised as a Execute tool in the BoltzGen MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the BoltzGen MCP server in PolicyLayer and add a rule for boltzgen_submit: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches BoltzGen MCP. Nothing to install.
boltzgen_submit is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the boltzgen_submit rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for boltzgen_submit. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
boltzgen_submit is provided by the BoltzGen MCP server (macromnex/boltzgen_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →