term_sheet_negotiation
Négociation term sheet — Gapup agent-payable C-suite expertise (FUNDRAISING). Returns a structured, audited deliverable. Reference case: Agicap Série C €50M — 8 clauses analysées · 3 rouges · Score fondateur 62/100 → plan pour 81. Inputs are validated server-side — send the documented case fields.
This record as markdown: /tools/io-github-getgapup-mcp-knowledge/term-sheet-negotiation.md
What term_sheet_negotiation does on Mcp Knowledge
AI agents call term_sheet_negotiation as a supporting operation in Mcp Knowledge workflows.
| 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 |
round | object | Yes | |
company | object | Yes | |
termSheetClauses | array | Yes |
Parameters from the server's own tool schema.
Why term_sheet_negotiation is rated Low
This tool appears to generate advisory analysis and structured deliverables related to term sheet negotiation for fundraising. It does not directly move money, delete data, execute code, or write to a system — it returns an analytical/expert report. However, its outputs could influence significant financial decisions.
From the tool's definition Négociation term sheet — Gapup agent-payable C-suite expertise (FUNDRAISING). Returns a structured, audited deliverable.
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs term_sheet_negotiation 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 term_sheet_negotiation, this is the rule to start with:
term_sheet_negotiation 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 term_sheet_negotiation call is checked against it from then on.
Questions about term_sheet_negotiation
Négociation term sheet — Gapup agent-payable C-suite expertise (FUNDRAISING). Returns a structured, audited deliverable. Reference case: Agicap Série C €50M — 8 clauses analysées · 3 rouges · Score fondateur 62/100 → plan pour 81. 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.
term_sheet_negotiation accepts 4 parameters: async, round, company, termSheetClauses. Required: round, company, termSheetClauses. 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 term_sheet_negotiation: 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.
term_sheet_negotiation 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 term_sheet_negotiation 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 term_sheet_negotiation. 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.
term_sheet_negotiation 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