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-mcp-knowledge/ma-deal-screener.md
What ma_deal_screener does on Mcp Knowledge
AI agents call ma_deal_screener to retrieve information from Mcp Knowledge 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 | — | |
acquirer | object | Yes | |
criteria | object | Yes |
Parameters from the server's own tool schema.
Why ma_deal_screener is rated Low
The tool screens and scores M&A targets, returning analytical deliverables (fit scores, valuations, integration risk assessments). This is fundamentally a read/query/analysis operation — it retrieves and structures intelligence rather than executing transactions or committing financial obligations.
From the tool's definition M&A Deal Screener — Returns a structured, audited deliverable... fit score + valuation + integration risk
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 Mcp Knowledge, 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:
ma_deal_screener 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 Mcp Knowledge, 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 Read tool in the Mcp Knowledge MCP Server, which means it retrieves data without modifying state.
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 Mcp Knowledge 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 Mcp Knowledge. Nothing to install.
ma_deal_screener 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 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 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