audit_pre_flight
Pré-audit comptable — Gapup agent-payable C-suite expertise (CFO). Returns a structured, audited deliverable. Reference case: Spendesk — Pré-audit commissaire · Readiness 74/100 · 4 findings critiques · Checklist 18 docs. Inputs are validated server-side — send the documented case fields.
This record as markdown: /tools/io-github-getgapup-gapup-mcp/audit-pre-flight.md
What audit_pre_flight does on Gapup Mcp
AI agents use audit_pre_flight to commit financial operations through Gapup Mcp, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| 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 |
audit | object | Yes | |
company | object | Yes | |
systems | array | Yes | |
financials | object | Yes | |
knownIssues | array | Yes |
Parameters from the server's own tool schema.
Why audit_pre_flight is rated Critical
This tool is explicitly 'agent-payable' with a per-call financial charge (x402 protocol), meaning each invocation commits a financial transaction. The tool itself performs accounting pre-audit analysis (CFO-level), which is a financial compliance function. The combination of per-call payment obligation and financial/accounting subject matter places this firmly in the Financial category.
From the tool's definition Pré-audit comptable — Gapup agent-payable C-suite expertise (CFO)... x402 per-call
Risk signalsHigh parameter count (16 properties)
Attacks that exploit this kind of access
The rule that runs audit_pre_flight 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 audit_pre_flight, this is the rule to start with:
Any call to audit_pre_flight is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Gapup Mcp, apply this rule, and every audit_pre_flight call is checked against it from then on.
Questions about audit_pre_flight
Pré-audit comptable — Gapup agent-payable C-suite expertise (CFO). Returns a structured, audited deliverable. Reference case: Spendesk — Pré-audit commissaire · Readiness 74/100 · 4 findings critiques · Checklist 18 docs. Inputs are validated server-side — send the documented case fields. It is categorised as a Financial tool in the Gapup Mcp MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
audit_pre_flight accepts 6 parameters: async, audit, company, systems, financials, knownIssues. Required: audit, company, systems, financials, knownIssues. 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 audit_pre_flight: 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.
audit_pre_flight is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the audit_pre_flight 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 audit_pre_flight. 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.
audit_pre_flight 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.
Across the catalogue