> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/scan-fix-and-prevent/prevent/policies/security-policies/security-policy-actions.md).

# Security policy actions

An action defines what you want to happen when the [security policy conditions](/scan-fix-and-prevent/prevent/policies/security-policies/security-policies-conditions.md) are matched.

{% hint style="info" %}
You cannot stack multiple actions in the same rule. To have multiple actions with a rule, create a new rule block with the same conditions, and specify a different action.
{% endhint %}

These are the actions that can currently be applied:

<table><thead><tr><th width="164">Action</th><th>Definitions</th></tr></thead><tbody><tr><td>Change severity to…</td><td><p>Changes the severity of whatever issues match the conditions. This can be set to <code>Low</code>, <code>Medium</code>, <code>High</code>, or <code>Critical</code>.<br></p><p>Issues with a changed severity have their <a href="/pages/5bKH8JgifXeO3mjK9g5V">priority score </a>updated to reflect the new severity. A note appears on the <a href="/pages/o0117DTy5gLKQsOA3WlA">issue card</a> indicating that the severity of the issue has been changed by a policy. The severity icon will also be "stacked," showing the original severity behind the new one.</p></td></tr><tr><td>Ignore current and future instances</td><td><p>Ignore all vulnerabilities that match the conditions. For example, ignore all issues that have no known exploits in Projects with a <code>business</code> <code>criticality</code> attribute of <code>low</code>.</p><p>After an ignore policy is applied, ignores will occur every time the relevant Project is re-scanned, with ignored issues marked as <code>ignored by Security Policy</code>.</p><p>When setting the action, you can select <code>won't fix</code> and <code>not vulnerable</code> as ignore types, and add a reason, which appears with the ignore on the issue card</p><p>Policy-based ignores have the same behavior as issues that are manually ignored. As with manual ignores, automatic PRs are not raised on issues ignored by a security policy or included in the issue count in reporting.</p></td></tr></tbody></table>

{% hint style="info" %}
Security policies are applicable to Snyk Open Source and Snyk Container Projects.
{% endhint %}


---

# 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://docs.snyk.io/scan-fix-and-prevent/prevent/policies/security-policies/security-policy-actions.md?ask=<question>&goal=<endgoal>
```

`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.