contract_risk_scanner
Scanner de risques contractuels — Gapup agent-payable C-suite expertise (RISK). Returns a structured, audited deliverable. Reference case: Salesforce MSA — revue d'un client SaaS B2B EMEA. Inputs are validated server-side — send the documented case fields.
This record as markdown: /tools/io-github-getgapup-gapup-mcp/contract-risk-scanner.md
What contract_risk_scanner does on Gapup Mcp
AI agents call contract_risk_scanner to retrieve information from Gapup Mcp 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 |
focus | string | — | |
contractText | string | Yes | |
contractContext | object | Yes |
Parameters from the server's own tool schema.
Why contract_risk_scanner is rated Low
The tool scans and analyzes contractual risk, returning a structured audit report. This is primarily a read/analysis operation — it retrieves and processes contract data to identify risks, with no indication it modifies, deletes, or executes anything. However, the 'x402 per-call' payment model on the server description means each invocation carries a financial micro-transaction, slightly elevating concern.
From the tool's definition Scanner de risques contractuels — Returns a structured, audited deliverable. Reference case: Salesforce MSA — revue d'un client SaaS B2B EMEA.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs contract_risk_scanner 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 contract_risk_scanner, this is the rule to start with:
contract_risk_scanner 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 Gapup Mcp, apply this rule, and every contract_risk_scanner call is checked against it from then on.
Questions about contract_risk_scanner
Scanner de risques contractuels — Gapup agent-payable C-suite expertise (RISK). Returns a structured, audited deliverable. Reference case: Salesforce MSA — revue d'un client SaaS B2B EMEA. Inputs are validated server-side — send the documented case fields. It is categorised as a Read tool in the Gapup Mcp MCP Server, which means it retrieves data without modifying state.
contract_risk_scanner accepts 4 parameters: async, focus, contractText, contractContext. Required: contractText, contractContext. The full parameter table on this page comes from the server's own tool schema.
Register the Gapup MCP server in PolicyLayer and add a rule for contract_risk_scanner: 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.
contract_risk_scanner 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 contract_risk_scanner 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 contract_risk_scanner. 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.
contract_risk_scanner 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.
More on Gapup, and thousands of servers like it.
This server
Across the catalogue