ma_deal_screener
M&A Deal Screener — Gapup agent-payable C-suite expertise (CSO). Returns a structured, audited deliverable. Reference case: Salesforce M&A targets — 12 cibles screened · fit score + valuation + integration risk. Inputs are validated server-side — send the documented case fields.
This record as markdown: /tools/io-github-getgapup-gapup-mcp/ma-deal-screener.md
What ma_deal_screener does on Gapup Mcp
AI agents use ma_deal_screener 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 |
focus | string | — | |
acquirer | object | Yes | |
criteria | object | Yes |
Parameters from the server's own tool schema.
Why ma_deal_screener is rated Critical
This tool screens mergers and acquisitions targets, including valuation and integration risk assessments. M&A decisions directly commit or influence major financial transactions and obligations. The 'agent-payable' model means each call incurs a financial cost, and the outputs guide high-value financial deals.
From the tool's definition M&A Deal Screener — fit score + valuation + integration risk; agent-payable; 12 cibles screened
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs ma_deal_screener 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 ma_deal_screener, this is the rule to start with:
Any call to ma_deal_screener 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 ma_deal_screener call is checked against it from then on.
Questions about ma_deal_screener
M&A Deal Screener — Gapup agent-payable C-suite expertise (CSO). Returns a structured, audited deliverable. Reference case: Salesforce M&A targets — 12 cibles screened · fit score + valuation + integration risk. 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.
ma_deal_screener accepts 4 parameters: async, focus, acquirer, criteria. Required: acquirer, criteria. 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 ma_deal_screener: 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.
ma_deal_screener 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 ma_deal_screener 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 ma_deal_screener. 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.
ma_deal_screener 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