attack_surface_monitor
Surveillance surface d'attaque — Gapup agent-payable C-suite expertise (RISK). Returns a structured, audited deliverable. Answers: Which Internet-facing assets of <domain> combine a critical CVE, an exposed service, and no WAF — top findings to fix in 14 days? · What is the attack surface of <dom...
This record as markdown: /tools/io-github-getgapup-gapup-mcp/attack-surface-monitor.md
What attack_surface_monitor does on Gapup Mcp
AI agents call attack_surface_monitor 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 | — | |
domain | string | Yes | |
exclusions | array | — | |
scope_cidrs | array | — | |
include_email_surface | boolean | Yes |
Parameters from the server's own tool schema.
Why attack_surface_monitor is rated Low
Despite the intimidating name and C-suite risk framing, attack_surface_monitor is fundamentally a reconnaissance and assessment tool that gathers information about a target domain's security configuration and vulnerabilities. It does not execute exploits, modify systems, delete data, or trigger payments.
From the tool's definition Tool returns 'structured, audited deliverable' answering questions about 'Internet-facing assets', 'attack surface', 'subdomains, open ports, SSL/TLS grades', 'CVEs', 'phishing risk', 'SPF/DMARC posture', and produces 'ASM report' and 'remediation plan'.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs attack_surface_monitor 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 attack_surface_monitor, this is the rule to start with:
attack_surface_monitor 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 attack_surface_monitor call is checked against it from then on.
Questions about attack_surface_monitor
Surveillance surface d'attaque — Gapup agent-payable C-suite expertise (RISK). Returns a structured, audited deliverable. Answers: Which Internet-facing assets of <domain> combine a critical CVE, an exposed service, and no WAF — top findings to fix in 14 days? · What is the attack surface of <domain>: subdomains, open ports, SSL/TLS grades, and associated CVEs? · Give me a CISO-ready ASM report with blast radius estimate and SLA-driven remediation plan for <domain>. · What is the email phishing risk for <domain>? Assess SPF/DMARC posture and recommend improvements. · During M&A due diligence, what are the top cyber exposures on <domain>'s Internet-facing infrastructure? Reference case: Velora Payments — 8 assets exposés · 2 critiques (CVE-2023-44487 HTTP/2 RapidReset, Admin panel ouvert) · . 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.
attack_surface_monitor accepts 6 parameters: async, focus, domain, exclusions, scope_cidrs, include_email_surface. Required: domain, include_email_surface. 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 attack_surface_monitor: 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.
attack_surface_monitor 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 attack_surface_monitor 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 attack_surface_monitor. 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.
attack_surface_monitor 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