> For the complete documentation index, see [llms.txt](https://guardian.hedera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guardian.hedera.com/docs/3.5.1/guardian/standard-registry/policies/policy-creation/creating-a-policy-through-policy-configurator/policy-workflow-step-24-1.md).

# Policy Workflow Step 25

Next, we click on the “mint\_events”, and then add a mint action by clicking on the “Tokens” drop-down in the top navigation bar and selecting the “Mint” action.

Select the token you want to mint from the token drop down.

You can use the rule field to enter minting calculations that are specific to your policy. We define the Rule to be 1, meaning we will mint exactly the number of tokens defined in the MRV schema multiplied by 1.

Then we click on the “Save” button on the left side in the top navigation bar.

![](https://content.gitbook.com/content/EvaEsaNo09Ib5tjr1yj1/blobs/TZIFvXbfaqbSRylTYDPD/PW_image_31.png)

**Programmatically this workflow step looks like this:**

```
    //Minting
    {
      //"mintDocumentBlock" - receives the VC from the previous block and mints based on the rule[s].
      "blockType": "mintDocumentBlock",
      "tag": "mint_token",
      //"tokenId" - ID of the token
      // User should be previously linked with token.
      "tokenId": "0.0.26063342",
      // Rules under which the number of tokens is calculated. Math operations are supported, e.g. the following:
      //  data = { amount: 2 }
      //  rule = "amount * 10"
      // will result in 20 tokens.
      "rule": "1",
      "uiMetaData": {}
    }
  ]
}
```


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://guardian.hedera.com/docs/3.5.1/guardian/standard-registry/policies/policy-creation/creating-a-policy-through-policy-configurator/policy-workflow-step-24-1.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.