Generate de novo protein backbones using RFdiffusion.
AI agents invoke generate_backbone to trigger actions in Protein Design. 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.
This tool runs RFdiffusion, a computational protein design algorithm, to generate novel protein backbone structures. It executes an external computational process whose outputs depend on the input arguments. It does not simply read existing data, but actively runs a generative model to produce new structures.
From the tool's definition Generate de novo protein backbones using RFdiffusion
Documented attack patterns abuse exactly the kind of access generate_backbone gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Protein Design, and nothing reaches the server without passing your rules. This is the rule we recommend for generate_backbone:
{
"version": "1",
"default": "deny",
"tools": {
"generate_backbone": {
"limits": [
{
"counter": "generate_backbone_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}generate_backbone 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.
Free to start. No card required.
Generate de novo protein backbones using RFdiffusion. It is categorised as a Execute tool in the Protein Design MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Protein Design MCP server in PolicyLayer and add a rule for generate_backbone: 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 Protein Design. Nothing to install.
generate_backbone 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 generate_backbone 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 generate_backbone. 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.
generate_backbone is provided by the Protein Design MCP server (jasonkim8652/protein-design-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Protein Design, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
19 Protein Design tools catalogued and risk-classified — across an index of 43,000+ MCP servers.