graduate_to_production · Framedeck MCP: Risk & Policy

WHAT IT DOES

What graduate_to_production does on Framedeck

AI agents use graduate_to_production to create or update resources in Framedeck — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Framedeck environment.

WHY IT NEEDS A POLICY

Why graduate_to_production needs a policy

This tool creates a new production and transitions data (the card) from one location to another. This is a reversible state change with side effects, classifying it as Write rather than Execute (no code/command execution) or Destructive (the action can be undone by archiving or reverting the production).

From the tool's definition Tool description states 'Promote an idea' and 'Moves the idea card to' — indicates creation of a new production entity and modification of card state, both write operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

graduate_to_production Rate-limited

graduate_to_production stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "graduate_to_production": {
      "limits": [
        {
          "counter": "graduate_to_production_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about graduate_to_production

What does the graduate_to_production tool do? +

Promote an idea from the Idea Pool into its own dedicated production with full stages (Idea → Scripting → Filming → Editing → Published). Moves the idea card to. It is categorised as a Write tool in the Framedeck MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on graduate_to_production? +

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

What risk level is graduate_to_production? +

graduate_to_production is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit graduate_to_production? +

Yes. Add a rate_limit block to the graduate_to_production 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 graduate_to_production completely? +

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

graduate_to_production is provided by the Framedeck MCP server (lukaris/framedeck-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.