submit_async_design · BindCraft MCP: Risk & Policy

WHAT IT DOES

What submit_async_design does on BindCraft MCP

AI agents invoke submit_async_design to trigger actions in BindCraft 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.

WHY IT NEEDS A POLICY

Why submit_async_design needs a policy

The name 'submit_async_design' suggests submitting an asynchronous job, likely triggering execution of a BindCraft design pipeline in Docker. Sibling tools like 'bindcraft_submit' and 'cancel_job' support this interpretation. Without a description, confidence is reduced, but the most likely category is Execute given the computational/external operation context.

From the tool's definition Tool name 'submit_async_design' on a server for protein binder design via Docker; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit_async_design Rate-limited

submit_async_design stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "submit_async_design": {
      "limits": [
        {
          "counter": "submit_async_design_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches BindCraft MCP, so you can run agents against it safely.

FAQ

Questions about submit_async_design

What does the submit_async_design tool do? +

submit_async_design. It is categorised as a Execute tool in the BindCraft MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on submit_async_design? +

Register the BindCraft MCP server in PolicyLayer and add a rule for submit_async_design: 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 BindCraft MCP. Nothing to install.

What risk level is submit_async_design? +

submit_async_design is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit submit_async_design? +

Yes. Add a rate_limit block to the submit_async_design 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.

How do I block submit_async_design completely? +

Set action: deny in the PolicyLayer policy for submit_async_design. 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.

What MCP server provides submit_async_design? +

submit_async_design is provided by the BindCraft MCP server (macromnex/bindcraft_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.