battle_plan

SERVERGapup Mcp SOURCEhttps://mcp.gapup.io/mcp

Medium RISK CLASS

Category Write

Parameters 1110 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-getgapup-gapup-mcp/battle-plan.md

WHAT IT DOES

What battle_plan does on Gapup Mcp

AI agents use battle_plan to create or update resources in Gapup Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gapup Mcp 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
`quarter`	string	Yes
`teamSize`	number	Yes
`arrTarget`	number	Yes
`budgetEur`	number	Yes
`arrCurrent`	number	Yes
`companyName`	string	Yes
`topChannels`	array	Yes
`icpDescription`	string	Yes
`currentBlockers`	array	Yes
`primaryObjective`	string	Yes

Parameters from the server's own tool schema.

RISK

Why battle_plan is rated Medium

This tool creates/generates a new marketing plan deliverable (a Write action) based on input parameters. It does not query existing data (Read), execute arbitrary code or external operations (Execute), delete data (Destructive), or move money (Financial).

From the tool's definition Tool returns a 'structured, audited deliverable' and references a specific case with budget (€120k) and pipeline (€800k) figures. The name 'battle_plan' and description 'Plan de bataille marketing' indicate it creates a marketing plan document.

Risk signalsHigh parameter count (11 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs battle_plan safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Gapup Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For battle_plan, this is the rule to start with:

battle_plan Rate-limited

battle_plan 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": {
    "battle_plan": {
      "limits": [
        {
          "counter": "battle_plan_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gapup Mcp, apply this rule, and every battle_plan call is checked against it from then on.

FAQ

Questions about battle_plan

What does the battle_plan tool do? +

Plan de bataille marketing — Gapup agent-payable C-suite expertise (CMO). Returns a structured, audited deliverable. Reference case: Gapup Hub — Q3 2026 · Budget €120k · Pipeline €800k · 5 chantiers prioritaires. Inputs are validated server-side — send the documented case fields. It is categorised as a Write tool in the Gapup Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does battle_plan accept? +

battle_plan accepts 11 parameters: async, quarter, teamSize, arrTarget, budgetEur, arrCurrent, companyName, topChannels, icpDescription, currentBlockers, primaryObjective. Required: quarter, teamSize, arrTarget, budgetEur, arrCurrent, companyName, topChannels, icpDescription, currentBlockers, primaryObjective. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on battle_plan? +

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

What risk level is battle_plan? +

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

Can I rate-limit battle_plan? +

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

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

battle_plan is provided by the Gapup MCP server (https://mcp.gapup.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Gapup, and thousands of servers like it.

This server

All 271 Gapup tools →

Across the catalogue

team_manager_plan_room on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →