pricing_in_deal
Pricing en Deal — Gapup agent-payable C-suite expertise (CRO). Returns a structured, audited deliverable. Reference case: Agicap × Groupe Rocher — Deal €38k · stade négociation · contre-offre -30% · 3 scénarios pricing · ROI 12×. Inputs are validated server-side — send the documented case fields.
This record as markdown: /tools/io-github-getgapup-mcp-knowledge/pricing-in-deal.md
What pricing_in_deal does on Mcp Knowledge
AI agents call pricing_in_deal as a supporting operation in Mcp Knowledge workflows.
| Parameter | Type | Required | Description |
|---|---|---|---|
deal | object | Yes | |
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 | |
redLines | object | Yes | |
negotiationContext | object | Yes |
Parameters from the server's own tool schema.
Why pricing_in_deal is rated Low
This tool appears to generate pricing analysis and deal scenario recommendations (a structured advisory deliverable) rather than directly moving money, executing code, writing/modifying data, or deleting anything.
From the tool's definition 'Pricing en Deal — Gapup agent-payable C-suite expertise (CRO). Returns a structured, audited deliverable. Reference case: Agicap × Groupe Rocher — Deal €38k · stade négociation · contre-offre -30% · 3 scénarios pricing · ROI 12×'
Risk signalsHigh parameter count (30 properties)
Attacks that exploit this kind of access
The rule that runs pricing_in_deal 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 pricing_in_deal, this is the rule to start with:
pricing_in_deal gets a rate cap, and 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 pricing_in_deal call is checked against it from then on.
Questions about pricing_in_deal
Pricing en Deal — Gapup agent-payable C-suite expertise (CRO). Returns a structured, audited deliverable. Reference case: Agicap × Groupe Rocher — Deal €38k · stade négociation · contre-offre -30% · 3 scénarios pricing · ROI 12×. Inputs are validated server-side — send the documented case fields. It is categorised as a Other tool in the Mcp Knowledge MCP Server, which means it performs auxiliary operations.
pricing_in_deal accepts 5 parameters: deal, async, company, redLines, negotiationContext. Required: deal, company, redLines, negotiationContext. 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 pricing_in_deal: 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.
pricing_in_deal is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the pricing_in_deal 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 pricing_in_deal. 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.
pricing_in_deal 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