> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/automations/scripts/use-existing-scripts.md). # Use existing scripts Using or modifying an existing script enables you to quickly leverage proven functionality and save significant time and effort developing a new script from scratch. For example, you can use scripts from the Base and Common Scripts content packs that provide basic and reusable functions that can streamline your playbook development.
Common scripts Filter and sort the table Use the filter bar at the top of the Secrets table to narrow results by any filterable column. Common filtering strategies include: **By severity:** Filter to Critical and High severity to focus on the most impactful secrets exposures **By secret type:** Filter to a specific secret type (such as AWS Access Key) to scope remediation to a single credential category * **By branch:** Filter to the main or production branch to focus on secrets that affect production-bound code **By resolution status:** Filter to New to identify untriaged secrets issues, or to In Progress to monitor active remediation **By secret validation:** Filter to Valid or Privileged to identify confirmed active credentials that require immediate revocation You can copy the script and add new functions/variables, or add your functions to the **CommonUserServer** script. You can also use your scripts to override the existing scripts in the **CommonServer** script. * **CommonServerPython** The **CommonServerPython** script contains Python functions that can be used when writing your scripts and integrations. The script contains over 400 functions, such as **`appendContext`**, **`vtCountPositives`** (which counts the number of detected URLs in the War Room entry), and **`datetime_to_string`**, (which converts a DateTime object into a string). You can copy the script and add new functions/variables, or add your functions to the **CommonServerUserPython** script. You can also use your scripts to override the existing scripts in the **CommonServerPython** script. * **CommonServerPowerShell** The **CommonServerPowerShell** script contains PowerShell arguments/functions that can be used when writing your scripts and integrations. The script contains many arguments/functions, such as **`SetIntegrationContext`**, **`Write-HostToLog`** (which writes to the demisto.log), and **`ReturnOutputs`** (which returns results to the user more intuitively). You can copy the script and add new arguments/functions or add your own to the **CommonServerUserPowerShell** script. You can also use your scripts to override the existing scripts in the **CommonServerPowerShell** script.
1. Navigate to **Investigation & Response** → **Automation** → **Scripts** and in the **Scripts Library** search for the script you want to use. * Use the free text in the search box to find an existing script. From the search drop-down, you can: * Perform a basic search by **Basic** (name and tag), **Name**, or **Tag**. * Perform an advanced search for specific words **In Script** or **Everywhere** (including the script name and tags). * You can search for an exact match of the script name by putting quotation marks around the search text. For example, searching for **`"AddKeyToList"`** returns the script with that name. You can search for more than one exact match by including the logical operator "or" in between your search texts in quotation marks. For example, searching for **`"AnalyzeTimestampIntervals" or "AddKeyToList"`** returns the two scripts with those names. Wildcards are not supported in free text search. * You can sort the scripts in the library alphabetically, by modified date, by system, or custom, and you can filter for disabled or deprecated scripts. * The [Script Helper](https://xsoar.pan.dev/docs/concepts/xsoar-ide#the-script-helper) also provides a list of available alphabetically ordered commands and scripts. 2. Click **Edit**. If the script you want to use is locked, you first need to duplicate it. If a script is installed from a content pack, by default, the script is locked, which means that it is not editable. 3. In the **Agentic Assistant** pane, start a conversation with the Automation Engineer agent to edit the script, or manually edit the script code and define the script settings. For more information, see [Automation Engineer for scripts](/cortex-xsiam/configure-cortex-xsiam/automations/scripts/accelerate-script-development-using-the-automation-engineer-agent.md). For details about script settings, see [Create a script](/cortex-xsiam/configure-cortex-xsiam/automations/scripts/create-a-script.md). 4. Save the script version. 5. (Recommended) Validate your script. 1. Click **Test**. 2. In the **Arguments** section, provide values for any inputs your prompt requires. These inputs are used to simulate how the script will behave in a live playbook, or how the script registered as an Action and assigned to an Agent will run as part of an executed plan. You can add input values manually. 3. Click **Run**. The scripts are executed in the Playground. Review the script's output to validate its behavior and ensure it produces the expected results. The output is typically a text summary or another structured format that you have defined. In each run result, you can take the following actions: | Action | Description | | ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Edit | Edit the entry, mark it as a note, preview it, or delete it. | | Mark as note |

Marks the entry as a note, which can help you understand why certain action was taken and assist future decisions.

When marked as a note, it is highlighted, so you can easily find it in the War Room or the Issue Overview tab.

| | View artifact in new tab | Opens a new tab for the artifact. | | Add tags | Add any relevant tags to use that help you find relevant information. | 6. (Optional) Click next to the Edit button, then select Register new Action to register the script as an action and make it available to agents. For more information, see [Manage actions](/cortex-xsiam/configure-cortex-xsiam/configure-the-cortex-agentic-assistant-1/agents-hub/manage-actions.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/automations/scripts/use-existing-scripts.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.