---
sourceDocument: Australia Enable AI
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/intelligent-experiences

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Enable AI

ft:clusterId :

    - platai

bundleId :

    - platai

workflow :

    - Platform


---

# MID keystore AI agent

# MID keystore AI agent {#ariaid-title1}

Release version: Australia  
Updated August 14, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
This AI agent helps IT administrators diagnose and resolve MID Server keystore problems and manage MID Server health.

## Workflow {#plat-mid-mid-keystore-ai-agent__zsmdlwierhjt}

The agent fetches MID Server and issue details, executes rekey and validation operations, provides step-by-step recovery instructions, and ensures the MID Server returns to a validated state.

1. Identify the keystore issue from the user prompt or from the issue table.
2. If the MID Server is up, walk the user through the rekeying process.
3. If the MID Server is down, walk the user through troubleshooting steps.
4. Validate the resolution.
5. If the user verifies that the issue is resolved, end execution. Otherwise, restart the process.
{#plat-mid-mid-keystore-ai-agent__ol_hcp_qwx_njc}  
{#plat-mid-mid-keystore-ai-agent__zsmdlwierhjt__entry__2}

| Field | Description |
|-|-|
| Allow third party to access this AI agent | When enabled, third-party AI agents can use this agent. This value is off (false) by default. This setting is defined in the AI Agent configs \[sn_aia_agent_config\] table on the External discoverable field. |
| Allow AI specialists to access this AI agent | When enabled, AI specialists can use this agent. This value is off (false) by default. When set to true, more configuration options for tools become available so that an AI specialist can map inputs and response templates to tool outputs. This setting is defined in the AI Agent configs \[sn_aia_agent_config\] table on the Specialist enabled field. |
| Manage long-term memory | When enabled, all previous user interactions are used as context for the LLM. This value is off (false) by default. This setting is defined by the sn_aia.ltm.enable_long_term_memory system property. For more information, see [ServiceNow Otto AI agents reference](https://www.servicenow.com/docs/MUqSU8rHp3ao~q3QEWgHkA "Find more information about user roles, tables, and the different properties that are installed in ServiceNow Otto AI agents."). |
| Tools | Scripts :   Fetch a MID server details :   Fetch keystore issues :   MID script retriever :   Rekey a MID server :   Validate/Invalidate a MID server Subflows :   Verify rekey completion :   Verify rekey trigger :   Verify validation completion |
| Allowed user roles The specific user roles that can access this AI agent. | sn_itom_mid_grdn.admin |
| Data access roles The specific user identity roles that determine which data the AI agent can access and what actions it can take. | sn_itom_mid_grdn.admin |
| Triggers | Optional. None defined by default. An admin can specify triggers if desired. For more information, see [Add a trigger to an AI agent](https://www.servicenow.com/docs/NXqRJBQV_Vw00FEzklcAJw "In the guided setup for an AI agent, add triggers to run the AI agent automatically when certain conditions are met."). |
| Channels | Not defined. |
| Used in agentic workflows | MID Guardian |
[Table 1. Configuration]

Learn more about MID Server management in [MID Server](https://www.servicenow.com/docs/access?context=mid-server-landing&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US).