> For the complete documentation index, see [llms.txt](https://docs.sealsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealsecurity.io/reference/mcp-server/tool-catalog.md). # Tool catalog The tools the Seal MCP server exposes, grouped by area. The Seal MCP server exposes the tools below, grouped by area. Each tool's exact arguments and response shape are advertised through the MCP protocol itself; this page is the reference list. ## Discovery and packages | Tool | What it does | | ----------------------------------- | ----------------------------------------------------------------------- | | `get_vulnerable_packages_snapshots` | Return a snapshot of the tenant's vulnerable packages. | | `set_activities_visibility` | Set the hide/restore visibility on one or more vulnerable-package rows. | | `list_used_packages` | List the packages currently in use in a Seal Project. | | `get_package_details` | Fetch the detail view for a specific package version. | | `get_package_artifacts` | List the artifacts available for a specific package version. | | `search_packages` | Search the Repository for packages by name. | | `scan_dockerfiles` | Scan one or more `Dockerfile` paths for vulnerable bases or packages. | | `scan_project` | Run a remote scan against a Seal Project. | ## Sealing Rules | Tool | What it does | | --------------------- | ------------------------------ | | `list_sealing_rules` | List the active Sealing Rules. | | `create_sealing_rule` | Create a new Sealing Rule. | | `delete_sealing_rule` | Delete a Sealing Rule. | ## Generate fix | Tool | What it does | | ----------------------------------- | ------------------------------------------------------ | | `create_generate_fix_request` | Request a new sealed version for one or more packages. | | `get_generate_fix_requests_summary` | Query the status of pending Generate fix requests. | ## Projects | Tool | What it does | | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `list_projects` | List the tenant's Seal Projects. | | `create_project` | Create a Seal Project. | | `update_project` | Update a Seal Project's metadata. | | `set_project_state` | Change a Seal Project's lifecycle state (archive, restore). | | `get_project_statistics` | Aggregate statistics for a Seal Project. | | `create_ci_pull_request` | Open a pull request that integrates the Seal CLI into a Seal Project's CI configuration. | | `open_pull_request` | Open a pull request that fixes a GitHub-connected Seal Project's vulnerable packages by writing the proposed sealed-version rules into its `.seal-actions.yml` file. | ## Dashboard and analytics | Tool | What it does | | ---------------------- | ---------------------------------------------------------------- | | `get_daily_analytics` | Daily aggregates for the Dashboard. | | `get_usage_statistics` | Tenant-wide usage data; equivalent to what the Usage page shows. | ## Reports Reports are generated asynchronously: the create tools return immediately with a report in progress, and you poll `get_report` or `list_reports` until the report completes and its download URL is available. These map to the report types in the [Reports Manager](/using-platform/reports-manager.md). | Tool | What it does | | ----------------------------------- | ------------------------------------------------------------------------------------------------------------- | | `list_reports` | List the reports generated for the tenant, with optional filtering by report type, status, and creation date. | | `get_report` | Fetch a single report by ID, including its status and download URL once complete. | | `create_sealed_packages_report` | Generate a sealed-packages report (CSV or PDF). | | `create_vulnerable_packages_report` | Generate a vulnerable-packages report (CSV or PDF). | | `create_roi_report` | Generate an ROI report (PDF). | ## GitHub integration | Tool | What it does | | ------------------------------ | ------------------------------------------------------------------------------- | | `connect_github` | Initiate the GitHub App installation handoff. | | `list_github_repositories` | List the GitHub repositories accessible to the connected App installation. | | `get_github_repository_info` | Fetch metadata about a specific repository. | | `get_github_file_content` | Read a file from a connected GitHub repository. | | `create_seal_token_for_github` | Create a Seal token scoped to a GitHub repository for use inside a CI workflow. | ## Integration configuration | Tool | What it does | | ------------------------ | ------------------------------------------------------------------------------- | | `get_integration_config` | Read the configuration for a connected integration (Slack, GitHub, Snyk, etc.). | ## Users and permissions These tools are read-only and mirror what the Settings Users and Permissions page shows; they do not change roles, permissions, or membership. | Tool | What it does | | -------------------- | ----------------------------------------------------------------------------------------------------------------------------- | | `list_tenant_users` | List the tenant's users with the role(s) assigned to each, plus the tenant's roles. Requires the account-settings permission. | | `get_my_permissions` | Return the current caller's own identity and assigned role name(s); available to any authenticated caller. | ## Seal documentation Your MCP client also gets access to Seal's public documentation on the same endpoint, so no second server is needed for documentation search. | Tool | What it does | | -------------------------- | -------------------------------------------- | | `docs_searchDocumentation` | Semantic search over the Seal documentation. | | `docs_getPage` | Fetch a documentation page as markdown. | ## Tool gating The tools your client sees on connect are the subset your tenant and your user's permissions allow: * **Tenant feature flags.** Some tools are enabled per tenant. Contact your Seal account team if a tool you need is missing. * **Permissions.** Each tool requires a specific permission on the calling user. See [Permissions and tenant scoping](/reference/mcp-server/what-it-is.md#permissions-and-tenant-scoping). ## Related * [What the MCP server is](/reference/mcp-server/what-it-is.md) * [Using the MCP server from your own client](/reference/mcp-server/using-from-your-client.md)