pentest_scope_estimator

SERVERMcp Knowledge SOURCEhttps://mcp.gapup.io

Low RISK CLASS

Category Read

Parameters 93 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-getgapup-mcp-knowledge/pentest-scope-estimator.md

WHAT IT DOES

What pentest_scope_estimator does on Mcp Knowledge

AI agents call pentest_scope_estimator 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
`scope_type`	string	Yes
`tech_stack`	array	Yes
`asset_count`	integer	—
`target_geos`	array	—
`engagement_type`	string	—
`retest_included`	boolean	—
`business_context`	string	Yes
`compliance_frameworks`	array	—

Parameters from the server's own tool schema.

RISK

Why pentest_scope_estimator is rated Low

This tool is an estimator/advisor that returns structured information and recommendations about penetration testing scope, cost, effort, and engagement plans. It reads/analyzes inputs and returns advisory deliverables — it does not execute any tests, modify data, or trigger any external operations. It is purely informational/consultative in nature.

From the tool's definition Estimateur de scope pentest — Returns a structured, audited deliverable. Answers questions about effort and cost estimates, budget, engagement plans, and prerequisites for pentest engagements.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pentest_scope_estimator 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 pentest_scope_estimator, this is the rule to start with:

pentest_scope_estimator Allowed

pentest_scope_estimator is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pentest_scope_estimator": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Knowledge, apply this rule, and every pentest_scope_estimator call is checked against it from then on.

FAQ

Questions about pentest_scope_estimator

What does the pentest_scope_estimator tool do? +

Estimateur de scope pentest — Gapup agent-payable C-suite expertise (RISK). Returns a structured, audited deliverable. Answers: For a <scope_type> pentest on <tech_stack> with <N> assets, what is the effort and cost estimate? · How much should I budget for a web application + API penetration test for SOC 2 Type II compliance? · What is the standard engagement plan (PTES phases + deliverables) for a <scope_type> pentest? · Which engagement type (black-box/grey-box/white-box/red-team) is recommended for my context? · What are the prerequisites and risks for a pentest engagement on my cloud infrastructure? Reference case: Acme SaaS Inc — Fintech B2B EU · web-app + API REST · 12 microservices Node.js AWS · . 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.

What parameters does pentest_scope_estimator accept? +

pentest_scope_estimator accepts 9 parameters: async, scope_type, tech_stack, asset_count, target_geos, engagement_type, retest_included, business_context, compliance_frameworks. Required: scope_type, tech_stack, business_context. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on pentest_scope_estimator? +

Register the Mcp Knowledge MCP server in PolicyLayer and add a rule for pentest_scope_estimator: 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.

What risk level is pentest_scope_estimator? +

pentest_scope_estimator is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit pentest_scope_estimator? +

Yes. Add a rate_limit block to the pentest_scope_estimator 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.

How do I block pentest_scope_estimator completely? +

Set action: deny in the PolicyLayer policy for pentest_scope_estimator. 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.

What MCP server provides pentest_scope_estimator? +

pentest_scope_estimator 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.

KEEP EXPLORING

More on Mcp Knowledge, and thousands of servers like it.

This server

All 271 Mcp Knowledge tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →