close_engagement

Close an engagement and mark it as completed.

SERVERPentest Ai SOURCE0xsteph/pentest-ai

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xsteph-pentest-ai/close-engagement.md

WHAT IT DOES

What close_engagement does on Pentest Ai

AI agents use close_engagement to create or update resources in Pentest Ai, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pentest Ai environment.

RISK

Why close_engagement is rated Medium

This tool updates engagement metadata by marking a record as completed. It is Write rather than Destructive because closure/marking complete is typically reversible (engagement can usually be reopened or re-opened).

From the tool's definition 'Close an engagement and mark it as completed' - modifies state of an engagement record, changing its status from active to completed. This is a reversible state change operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs close_engagement safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Pentest Ai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For close_engagement, this is the rule to start with:

close_engagement Rate-limited

close_engagement stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "close_engagement": {
      "limits": [
        {
          "counter": "close_engagement_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about close_engagement

What does the close_engagement tool do? +

Close an engagement and mark it as completed. It is categorised as a Write tool in the Pentest Ai MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on close_engagement? +

Register the Pentest Ai MCP server in PolicyLayer and add a rule for close_engagement: 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 Pentest Ai. Nothing to install.

What risk level is close_engagement? +

close_engagement is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit close_engagement? +

Yes. Add a rate_limit block to the close_engagement 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 close_engagement completely? +

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

close_engagement is provided by the Pentest Ai MCP server (0xsteph/pentest-ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Pentest Ai, and thousands of servers like it.

This server

All 51 Pentest Ai tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →