For the complete documentation index, see llms.txt. This page is also available as Markdown.

Patch Project Summary Fields

Description

Partially updates the project summary custom fields of an existing AttackForge project. This is the write counterpart to find_project_summary_fields, and a write operation: only the keys present in args are modified - keys you omit are left untouched.

A two-step workflow is required because the input shape is tenant-specific - see Building args for Write Tools:

  1. Call get_args_schema_for_tool(tool="patch_project_summary_fields") to retrieve the current JSON Schema for args.

  2. Build args to match that schema and call this tool.

The schema always requires project_id (source: find_projects or find_project_summary_fields) plus custom_fields. Discover the summary custom-field keys with get_field_structure(model="project-summary"). Preconditions: the caller must have Edit access to the target project and access to its summary page; summary custom fields are additionally gated per field by the caller's edit access (view-only keys are silently ignored). On success the project id is returned.

How To Enable

  1. Go to Users

  2. Select the user you would like to provide access to this tool

  3. Click on Access > MCP

  4. Click on Add Tools

  5. Select the tool patch_project_summary_fields and click Add

Example Prompts

  • Set the engagement outcome summary field on project X to "Pass with remediation".

  • Update the summary page for the ACME project.

  • Fill in the summary custom fields for this project.

Parameters

Parameter
Type
Required
Description

args

object

Yes

The summary-fields patch payload. Build it to satisfy get_args_schema_for_tool(tool="patch_project_summary_fields"). Always requires project_id plus custom_fields; every supplied key applies a partial update.

Example Response

Last updated