generate_work_breakdown · ContextForge MCP Gateway MCP

WHAT IT DOES

What generate_work_breakdown does on ContextForge MCP Gateway

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

WHY IT NEEDS A POLICY

Why generate_work_breakdown needs a policy

This tool creates/generates a work breakdown structure (a new organizational artifact) based on input scope narrative. It does not delete, execute external commands, move money, or retrieve existing data—it synthesizes and writes new project planning data.

From the tool's definition Tool name 'generate_work_breakdown' and description 'Generate a work breakdown structure from scope narrative' indicate creation of new structured data output from input narrative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_work_breakdown Rate-limited

generate_work_breakdown 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": {
    "generate_work_breakdown": {
      "limits": [
        {
          "counter": "generate_work_breakdown_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 ContextForge MCP Gateway, so you can run agents against it safely.

FAQ

Questions about generate_work_breakdown

What does the generate_work_breakdown tool do? +

Generate a work breakdown structure from scope narrative. It is categorised as a Write tool in the ContextForge MCP Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on generate_work_breakdown? +

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

What risk level is generate_work_breakdown? +

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

Can I rate-limit generate_work_breakdown? +

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

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

generate_work_breakdown is provided by the ContextForge MCP Gateway MCP server (jrmatherly/mcp-context-forge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

generate_work_breakdown is one line of ContextForge MCP Gateway's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →