> For the complete documentation index, see [llms.txt](https://docs.bountysecurity.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bountysecurity.ai/creating-profiles/tags.md).

# Tags

Organize profiles for discovery, menu selection and rule actions.

Tags group profiles for context-menu selection, Smart Scan actions and MCP discovery. They do not define scanner type, vulnerability severity or execution order.

## In the profile editor

1. Open **Tags** in the profile editor.
2. Select an existing tag and use **Add** to assign it.
3. Use **New Tag** to create a category such as `Team-Reviewed`, then assign it to the profile.
4. Use **Remove** to remove an assignment and click **OK** to save.

Pro generates the saved tag list automatically. A profile can have tags such as SQLi, Database and Team-Reviewed without requiring JSON editing.

## Across the profile tables

Use the Tags column and **Tags Manager** to inspect categories. Use **Set New Tag** on selected profile rows to maintain organization. Apply tags to the intended active/passive table and check the enabled state before launching a menu selection.

A profile can have several tags. Selecting different tags in separate runs can select the same profile twice. The tag `All` is a convention in the pack and Pro interface, not a portable wildcard to assume in every API.

## In Server MCP

`list_profiles.tag` and `create_scan.profile_tags` use case-insensitive tag matching. Multiple requested tags select the union of matching profiles. Exact `profile_names` selection is preferable for reproducible batches or splitting work between servers.

Selecting one profile from a file does not include all its neighbors. Inline profiles retain their own metadata but are not installed into the catalogue.

## Naming conventions

Use unique profile names, stable category tags and explicit status tags for experimental checks. Avoid commas in names referenced by Pro rules, because the rule serialization uses comma-separated rows. Keep user-facing `IssueName` descriptions readable even when technical profile names are terse.