battle_plan
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.
This record as markdown: /tools/io-github-getgapup-mcp-knowledge/battle-plan.md
What battle_plan does on Mcp Knowledge
AI agents use battle_plan 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 |
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.
Why battle_plan is rated Medium
This tool generates marketing battle plans with financial parameters and strategic deliverables, which constitutes creating/modifying business data. It does not execute external campaigns (Execute), delete data (Destructive), or transfer funds (Financial)—it plans them.
From the tool's definition Tool returns 'structured, audited deliverable' and references budget/pipeline figures (€120k, €800k), indicating it creates or modifies strategic marketing plans.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs battle_plan 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 battle_plan, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Knowledge, apply this rule, and every battle_plan call is checked against it from then on.
Questions about battle_plan
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 Mcp Knowledge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
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.
Register the Mcp Knowledge 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 Mcp Knowledge. Nothing to install.
battle_plan 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 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.
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.
battle_plan 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