capacity_planning
Planification capacitaire — Gapup agent-payable C-suite expertise (CHRO). Returns a structured, audited deliverable. Reference case: Gapup Hub — 22→48 FTE en 12m · ARR €480k→€1.7M · Plan d'embauches par département. Inputs are validated server-side — send the documented case fields.
This record as markdown: /tools/io-github-getgapup-mcp-knowledge/capacity-planning.md
What capacity_planning does on Mcp Knowledge
AI agents use capacity_planning to create or update resources in Mcp Knowledge, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Knowledge environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
async | boolean | — | If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti |
company | object | Yes | |
benchmarks | object | — | |
financials | object | Yes | |
constraints | array | — | |
currentTeam | object | Yes | |
hiringBudgetEur | number | — |
Parameters from the server's own tool schema.
Why capacity_planning is rated Medium
This tool generates structured capacity planning deliverables (workforce scaling plans, hiring plans by department). It creates/produces a structured document or plan — a Write operation. It doesn't execute code, delete data, or directly move money. However, it could influence financial and hiring decisions, giving it medium severity if misused.
From the tool's definition Planification capacitaire — Returns a structured, audited deliverable. Reference case: 22→48 FTE en 12m · ARR €480k→€1.7M · Plan d'embauches par département.
Risk signalsHigh parameter count (22 properties)
Attacks that exploit this kind of access
The rule that runs capacity_planning safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Knowledge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For capacity_planning, this is the rule to start with:
capacity_planning 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Knowledge, apply this rule, and every capacity_planning call is checked against it from then on.
Questions about capacity_planning
Planification capacitaire — Gapup agent-payable C-suite expertise (CHRO). Returns a structured, audited deliverable. Reference case: Gapup Hub — 22→48 FTE en 12m · ARR €480k→€1.7M · Plan d'embauches par département. Inputs are validated server-side — send the documented case fields. It is categorised as a Write tool in the Mcp Knowledge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
capacity_planning accepts 7 parameters: async, company, benchmarks, financials, constraints, currentTeam, hiringBudgetEur. Required: company, financials, currentTeam. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Knowledge MCP server in PolicyLayer and add a rule for capacity_planning: 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 Mcp Knowledge. Nothing to install.
capacity_planning is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the capacity_planning 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 capacity_planning. 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.
capacity_planning is provided by the Mcp Knowledge MCP server (https://mcp.gapup.io). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Knowledge, and thousands of servers like it.
This server
Across the catalogue