battle_cards_live
Fiche de combat live — Gapup agent-payable C-suite expertise (CRO). Returns a structured, audited deliverable. Reference case: Gapup Hub vs McKinsey Lilli — Deal SaaS B2B €500k · Win rate +11 pts · 6 objections clés armées. Inputs are validated server-side — send the documented case fields.
This record as markdown: /tools/io-github-getgapup-mcp-knowledge/battle-cards-live.md
What battle_cards_live does on Mcp Knowledge
AI agents call battle_cards_live to retrieve information from Mcp Knowledge without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| 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 |
ourOffer | string | Yes | |
competitor | object | Yes | |
dealContext | object | Yes | |
knownWeaknesses | string | — |
Parameters from the server's own tool schema.
Why battle_cards_live is rated Low
The tool appears to generate/return competitive battle card analysis (CRO/sales intelligence content) based on input fields. It 'returns' a deliverable rather than modifying, executing, or deleting data. The description emphasizes output delivery ('Returns a structured, audited deliverable') with no indication of writes, deletions, or financial transactions.
From the tool's definition Returns a structured, audited deliverable... Inputs are validated server-side — send the documented case fields
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs battle_cards_live 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_cards_live, this is the rule to start with:
battle_cards_live is read-only, so it stays allowed. 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_cards_live call is checked against it from then on.
Questions about battle_cards_live
Fiche de combat live — Gapup agent-payable C-suite expertise (CRO). Returns a structured, audited deliverable. Reference case: Gapup Hub vs McKinsey Lilli — Deal SaaS B2B €500k · Win rate +11 pts · 6 objections clés armées. Inputs are validated server-side — send the documented case fields. It is categorised as a Read tool in the Mcp Knowledge MCP Server, which means it retrieves data without modifying state.
battle_cards_live accepts 5 parameters: async, ourOffer, competitor, dealContext, knownWeaknesses. Required: ourOffer, competitor, dealContext. 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_cards_live: 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_cards_live is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the battle_cards_live 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_cards_live. 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_cards_live 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