Skip to content
actionlake
Start free

Connectors · Identity & security

Qualys VMDR MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Qualys VMDR and the rest of your systems. It gives your agent 115 Qualys VMDR actions (40 reads, 51 writes and 24 that wait for a confirmation) and holds the Qualys VMDR credential itself, so the agent never does. It paces Qualys VMDR's limits and records every call.

Connect Qualys VMDR freeSee pricing

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp
the first call
do {  action: "qualys_vmdr.host_assets.search",  intent: "check which Qualys VMDR account is connected"}# Search host assets · read · 1 upstream call
  • 115actionsin one signed file
  • 40readlook, never change
  • 51writecreate and update
  • 24wait for a yesdestructive, confirmed first

Set up

Connect Qualys VMDR in three steps.

  1. 01

    Add actionlake to Claude.

    Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.

    https://connect.actionlake.com/mcp
  2. 02

    Connect Qualys VMDR.

    Username and secret. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.

    • usernameQualys user name with API access
    • passwordThat user's password
    • hostWhere your Qualys VMDR lives: your host
    account { op: "connections.requirements", service: "qualys_vmdr" }
# free: exactly what to paste, and what is found for you
  3. 03

    Make the first call. Check before a write.

    Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

    do    { action: "qualys_vmdr.host_assets.search" }# search host assets · read · 1 upstream callcheck { action: "qualys_vmdr.host_assets.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Qualys VMDR at a glance

Sign-in
Username and secret. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.
You provide
usernamepassword
Setup fields
host
Limits we pace to
300 calls an hour, per connection
API covered
Qualys Asset Management & Tagging API v2/v3 (QPS) and Cloud Agent API (QPS 1.0), at your Qualys VMDR instance's API base URL, which you enter when connecting
Built from
Qualys VMDR's documentation, read 22 October 2026docs.qualys.comdocs.qualys.com
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
40 of 40 reads, for up to 5 minutes; a write clears what it affects
Shared entities
1, so ask can line Qualys VMDR up with your other systems
Data
Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Qualys VMDR.

115 actions in 19 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

  • 40readlook, never change
  • 51writecreate and update
  • 24destructivewait for a confirmation

  1. Assets

    13

    3 read · 6 write · 4 destructive

    Count assets · Search assets · Activate modules on an asset · Activate modules on assets by filter

  2. Host assets

    12

    3 read · 5 write · 4 destructive

    Search host assets · Get a host asset · Create a host asset · Update a host asset

  3. Aws connectors V3

    10

    3 read · 5 write · 2 destructive

    Create an AWS connector 3.0 · Search AWS connector 3.0s · Download the AWS CloudFormation template (JSON) · Get an AWS connector 3.0

  4. Tags

    10

    3 read · 5 write · 2 destructive

    Count tags · Create a tag · Search tags · Re-evaluate a tag

  5. Asset data connectors

    9

    3 read · 4 write · 2 destructive

    Count asset data connectors · Search asset data connectors · Get an asset data connector · Run an asset data connector

  6. Azure connectors V3

    9

    2 read · 5 write · 2 destructive

    Create an Azure connector 3.0 · Search Azure connector 3.0s · Get an Azure connector 3.0 · Run an Azure connector 3.0

  7. GCP connectors V3

    9

    2 read · 5 write · 2 destructive

    Create a GCP connector 3.0 · Search GCP connector 3.0s · Get a GCP connector 3.0 · Run a GCP connector 3.0

  8. Aws connectors

    8

    3 read · 3 write · 2 destructive

    Count AWS asset data connector (v2)s · Create an AWS asset data connector (v2) · Search AWS asset data connector (v2)s · Get an AWS asset data connector (v2)

11 more areas · 35 actions
  • Activation keys 7
  • Azure connectors 7
  • Agent configs 5
  • Global scan configurations 3
  • Host instance vulns 3
  • Users 3
  • Agent scans 2
  • Aws base accounts V3 2
  • Agent binaries 1
  • Connector errors V3 1
  • Portal 1

Top actions

The Qualys VMDR API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 8 of Qualys VMDR's 9 action names are shared with at least one other connector, so an agent learns them once.

ActionWhat it doesEffectSame name in
qualys_vmdr.host_assets.searchSearch host assetsSearch host assets matching QPS filter criteria (one page; see preferences).readdevice.endpoint.search8 connectors
qualys_vmdr.host_assets.getGet a host assetReturn one host asset by id.readdevice.endpoint.get57 connectors
qualys_vmdr.host_assets.createCreate a host assetCreate a host asset.writedevice.endpoint.create12 connectors
qualys_vmdr.host_assets.deleteDelete a host assetDelete one host asset by id.destructivedevice.endpoint.delete35 connectors
qualys_vmdr.host_instance_vulns.getGet a host instance vulnerabilityReturn one host instance vulnerability by id.readsecurity.vulnerability.get11 connectors
qualys_vmdr.host_instance_vulns.searchSearch host instance vulnerabilitysSearch host instance vulnerabilitys matching QPS filter criteria (one page; see preferences).readsecurity.vulnerability.search4 connectors
qualys_vmdr.tags.countCount tagsCount tags matching QPS filter criteria.readthis connector
qualys_vmdr.tags.createCreate a tagCreate a tag.writethis connector
qualys_vmdr.users.countCount user (with tags)sCount user (with tags)s matching QPS filter criteria.readthis connector
qualys_vmdr.assets.countCount assetsCount assets matching QPS filter criteria.readthis connector
qualys_vmdr.users.searchSearch user (with tags)sSearch user (with tags)s matching QPS filter criteria (one page; see preferences).readthis connector
qualys_vmdr.agent_scans.launchLaunch an on-demand agent scan on one assetLaunch an on-demand Cloud Agent scan on one agent asset.writethis connector

Try it

Prompts to paste into Claude.

Each one names the Qualys VMDR actions it will call, so you know what it reads and what it changes before you send it.

  1. Readread

    Which Qualys VMDR devices have not checked in for a week?

    callsqualys_vmdr.host_assets.search

  2. Writewrite

    Create a host asset in Qualys VMDR. Show me exactly what you will send before you save it.

    callsqualys_vmdr.host_assets.create

Governance for Qualys VMDR

Destructive actions wait for a yes.

24 Qualys VMDR actions are destructive. These are all of them:

  • Delete a host assetqualys_vmdr.host_assets.delete
  • Delete a tagqualys_vmdr.tags.delete
  • Delete an assetqualys_vmdr.assets.delete
  • Uninstall the agent on an assetqualys_vmdr.assets.uninstall
  • Delete tags by filterqualys_vmdr.tags.delete_many
  • Delete assets by filterqualys_vmdr.assets.delete_many
  • Delete a Cloud Agent configuration profilequalys_vmdr.agent_configs.delete
  • Uninstall the agent on assets by filterqualys_vmdr.assets.uninstall_many
  • Delete an AWS asset data connector (v2)qualys_vmdr.aws_connectors.delete
  • Uninstall the agent on a host assetqualys_vmdr.host_assets.uninstall
  • Delete a Cloud Agent activation keyqualys_vmdr.activation_keys.delete
  • Delete an Azure asset data connector (v2)qualys_vmdr.azure_connectors.delete
  • Delete host assets by filterqualys_vmdr.host_assets.delete_many
  • Delete an AWS connector 3.0qualys_vmdr.aws_connectors_v3.delete
  • Delete a GCP connector 3.0qualys_vmdr.gcp_connectors_v3.delete
  • Delete AWS asset data connector (v2)s by filterqualys_vmdr.aws_connectors.delete_many
  • Delete an Azure connector 3.0qualys_vmdr.azure_connectors_v3.delete
  • Uninstall the agent on host assets by filterqualys_vmdr.host_assets.uninstall_many
  • Delete an asset data connectorqualys_vmdr.asset_data_connectors.delete
  • Delete Azure asset data connector (v2)s by filterqualys_vmdr.azure_connectors.delete_many
  • Delete AWS connector 3.0s by filterqualys_vmdr.aws_connectors_v3.delete_many
  • Delete GCP connector 3.0s by filterqualys_vmdr.gcp_connectors_v3.delete_many
  • Delete Azure connector 3.0s by filterqualys_vmdr.azure_connectors_v3.delete_many
  • Delete asset data connectors by filterqualys_vmdr.asset_data_connectors.delete_many

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

doqualys_vmdr.host_assets.deleteconfirm_policy: human

Delete a host asset?

intent: the user asked me to delete a host asset

run suspended · waiting for a named person · key qualys-vmdr-agent cannot confirm itself
In the console, or from an emailed signed link.
a key for this connector
account {  op: "keys.create", name: "qualys-vmdr-agent",  allowed_actions: ["qualys_vmdr.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "qualys_vmdr.host_assets.delete", approver: "[email protected]" },    { match: "qualys_vmdr.tags.delete", approver: "[email protected]" },    { match: "qualys_vmdr.assets.delete", approver: "[email protected]" }  ]}
Illustrative. Scoped to Qualys VMDR only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Qualys VMDR costs on actionlake.

Every Qualys VMDR action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Qualys VMDR refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

  • 1upstream call per actionall 115 Qualys VMDR actions
  • 115actions pageeach page of a long list is one call
  • 40reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Qualys VMDR action.

115 actions by area: the id your agent calls, what it does, and its effect.

Assets13
  • qualys_vmdr.assets.activateActivate modules on an assetwrite
  • qualys_vmdr.assets.activate_manyActivate modules on assets by filterwrite
  • qualys_vmdr.assets.countCount assetsread
  • qualys_vmdr.assets.deactivateDeactivate agent modules on an assetwrite
  • qualys_vmdr.assets.deactivate_manyDeactivate agent modules on assets by filterwrite
  • qualys_vmdr.assets.deleteDelete an assetdestructive
  • qualys_vmdr.assets.delete_manyDelete assets by filterdestructive
  • qualys_vmdr.assets.getGet an assetread
  • qualys_vmdr.assets.searchSearch assetsread
  • qualys_vmdr.assets.uninstallUninstall the agent on an assetdestructive
  • qualys_vmdr.assets.uninstall_manyUninstall the agent on assets by filterdestructive
  • qualys_vmdr.assets.updateUpdate an assetwrite
  • qualys_vmdr.assets.update_manyUpdate assets by filterwrite
Host assets12
  • qualys_vmdr.host_assets.activateActivate modules on a host assetwrite
  • qualys_vmdr.host_assets.activate_manyActivate modules on host assets by filterwrite
  • qualys_vmdr.host_assets.countCount host assetsread
  • qualys_vmdr.host_assets.createCreate a host assetwrite
  • qualys_vmdr.host_assets.deleteDelete a host assetdestructive
  • qualys_vmdr.host_assets.delete_manyDelete host assets by filterdestructive
  • qualys_vmdr.host_assets.getGet a host assetread
  • qualys_vmdr.host_assets.searchSearch host assetsread
  • qualys_vmdr.host_assets.uninstallUninstall the agent on a host assetdestructive
  • qualys_vmdr.host_assets.uninstall_manyUninstall the agent on host assets by filterdestructive
  • qualys_vmdr.host_assets.updateUpdate a host assetwrite
  • qualys_vmdr.host_assets.update_manyUpdate host assets by filterwrite
Aws connectors V310
  • qualys_vmdr.aws_connectors_v3.cloudformation_templateDownload the AWS CloudFormation template (JSON)read
  • qualys_vmdr.aws_connectors_v3.createCreate an AWS connector 3.0write
  • qualys_vmdr.aws_connectors_v3.deleteDelete an AWS connector 3.0destructive
  • qualys_vmdr.aws_connectors_v3.delete_manyDelete AWS connector 3.0s by filterdestructive
  • qualys_vmdr.aws_connectors_v3.getGet an AWS connector 3.0read
  • qualys_vmdr.aws_connectors_v3.runRun an AWS connector 3.0write
  • qualys_vmdr.aws_connectors_v3.run_manyRun AWS connector 3.0s by filterwrite
  • qualys_vmdr.aws_connectors_v3.searchSearch AWS connector 3.0sread
  • qualys_vmdr.aws_connectors_v3.updateUpdate an AWS connector 3.0write
  • qualys_vmdr.aws_connectors_v3.update_manyUpdate AWS connector 3.0s by filterwrite
Tags10
  • qualys_vmdr.tags.countCount tagsread
  • qualys_vmdr.tags.createCreate a tagwrite
  • qualys_vmdr.tags.deleteDelete a tagdestructive
  • qualys_vmdr.tags.delete_manyDelete tags by filterdestructive
  • qualys_vmdr.tags.evaluateRe-evaluate a tagwrite
  • qualys_vmdr.tags.evaluate_manyRe-evaluate tags by filterwrite
  • qualys_vmdr.tags.getGet a tagread
  • qualys_vmdr.tags.searchSearch tagsread
  • qualys_vmdr.tags.updateUpdate a tagwrite
  • qualys_vmdr.tags.update_manyUpdate tags by filterwrite
Asset data connectors9
  • qualys_vmdr.asset_data_connectors.countCount asset data connectorsread
  • qualys_vmdr.asset_data_connectors.deleteDelete an asset data connectordestructive
  • qualys_vmdr.asset_data_connectors.delete_manyDelete asset data connectors by filterdestructive
  • qualys_vmdr.asset_data_connectors.getGet an asset data connectorread
  • qualys_vmdr.asset_data_connectors.runRun an asset data connectorwrite
  • qualys_vmdr.asset_data_connectors.run_manyRun asset data connectors by filterwrite
  • qualys_vmdr.asset_data_connectors.searchSearch asset data connectorsread
  • qualys_vmdr.asset_data_connectors.updateUpdate an asset data connectorwrite
  • qualys_vmdr.asset_data_connectors.update_manyUpdate asset data connectors by filterwrite
Azure connectors V39
  • qualys_vmdr.azure_connectors_v3.createCreate an Azure connector 3.0write
  • qualys_vmdr.azure_connectors_v3.deleteDelete an Azure connector 3.0destructive
  • qualys_vmdr.azure_connectors_v3.delete_manyDelete Azure connector 3.0s by filterdestructive
  • qualys_vmdr.azure_connectors_v3.getGet an Azure connector 3.0read
  • qualys_vmdr.azure_connectors_v3.runRun an Azure connector 3.0write
  • qualys_vmdr.azure_connectors_v3.run_manyRun Azure connector 3.0s by filterwrite
  • qualys_vmdr.azure_connectors_v3.searchSearch Azure connector 3.0sread
  • qualys_vmdr.azure_connectors_v3.updateUpdate an Azure connector 3.0write
  • qualys_vmdr.azure_connectors_v3.update_manyUpdate Azure connector 3.0s by filterwrite
GCP connectors V39
  • qualys_vmdr.gcp_connectors_v3.createCreate a GCP connector 3.0write
  • qualys_vmdr.gcp_connectors_v3.deleteDelete a GCP connector 3.0destructive
  • qualys_vmdr.gcp_connectors_v3.delete_manyDelete GCP connector 3.0s by filterdestructive
  • qualys_vmdr.gcp_connectors_v3.getGet a GCP connector 3.0read
  • qualys_vmdr.gcp_connectors_v3.runRun a GCP connector 3.0write
  • qualys_vmdr.gcp_connectors_v3.run_manyRun GCP connector 3.0s by filterwrite
  • qualys_vmdr.gcp_connectors_v3.searchSearch GCP connector 3.0sread
  • qualys_vmdr.gcp_connectors_v3.updateUpdate a GCP connector 3.0write
  • qualys_vmdr.gcp_connectors_v3.update_manyUpdate GCP connector 3.0s by filterwrite
Aws connectors8
  • qualys_vmdr.aws_connectors.countCount AWS asset data connector (v2)sread
  • qualys_vmdr.aws_connectors.createCreate an AWS asset data connector (v2)write
  • qualys_vmdr.aws_connectors.deleteDelete an AWS asset data connector (v2)destructive
  • qualys_vmdr.aws_connectors.delete_manyDelete AWS asset data connector (v2)s by filterdestructive
  • qualys_vmdr.aws_connectors.getGet an AWS asset data connector (v2)read
  • qualys_vmdr.aws_connectors.searchSearch AWS asset data connector (v2)sread
  • qualys_vmdr.aws_connectors.updateUpdate an AWS asset data connector (v2)write
  • qualys_vmdr.aws_connectors.update_manyUpdate AWS asset data connector (v2)s by filterwrite
Activation keys7
  • qualys_vmdr.activation_keys.changeChange the activation key of agentswrite
  • qualys_vmdr.activation_keys.createCreate a Cloud Agent activation keywrite
  • qualys_vmdr.activation_keys.deleteDelete a Cloud Agent activation keydestructive
  • qualys_vmdr.activation_keys.getGet a Cloud Agent activation keyread
  • qualys_vmdr.activation_keys.searchSearch Cloud Agent activation keysread
  • qualys_vmdr.activation_keys.updateUpdate a Cloud Agent activation keywrite
  • qualys_vmdr.activation_keys.update_manyUpdate Cloud Agent activation keys by filterwrite
Azure connectors7
  • qualys_vmdr.azure_connectors.createCreate an Azure asset data connector (v2)write
  • qualys_vmdr.azure_connectors.deleteDelete an Azure asset data connector (v2)destructive
  • qualys_vmdr.azure_connectors.delete_manyDelete Azure asset data connector (v2)s by filterdestructive
  • qualys_vmdr.azure_connectors.getGet an Azure asset data connector (v2)read
  • qualys_vmdr.azure_connectors.searchSearch Azure asset data connector (v2)sread
  • qualys_vmdr.azure_connectors.updateUpdate an Azure asset data connector (v2)write
  • qualys_vmdr.azure_connectors.update_manyUpdate Azure asset data connector (v2)s by filterwrite
Agent configs5
  • qualys_vmdr.agent_configs.createCreate a Cloud Agent configuration profilewrite
  • qualys_vmdr.agent_configs.deleteDelete a Cloud Agent configuration profiledestructive
  • qualys_vmdr.agent_configs.getGet a Cloud Agent configuration profileread
  • qualys_vmdr.agent_configs.searchSearch Cloud Agent configuration profilesread
  • qualys_vmdr.agent_configs.update_manyUpdate Cloud Agent configuration profiles by filterwrite
Global scan configurations3
  • qualys_vmdr.global_scan_configurations.createCreate a global scan configurationwrite
  • qualys_vmdr.global_scan_configurations.searchSearch global scan configurationsread
  • qualys_vmdr.global_scan_configurations.update_manyUpdate global scan configurations by filterwrite
Host instance vulns3
  • qualys_vmdr.host_instance_vulns.countCount host instance vulnerabilitysread
  • qualys_vmdr.host_instance_vulns.getGet a host instance vulnerabilityread
  • qualys_vmdr.host_instance_vulns.searchSearch host instance vulnerabilitysread
Users3
  • qualys_vmdr.users.countCount user (with tags)sread
  • qualys_vmdr.users.getGet a user (with tags)read
  • qualys_vmdr.users.searchSearch user (with tags)sread
Agent scans2
  • qualys_vmdr.agent_scans.launchLaunch an on-demand agent scan on one assetwrite
  • qualys_vmdr.agent_scans.launch_manyLaunch an on-demand agent scan on assets by filterwrite
Aws base accounts V32
  • qualys_vmdr.aws_base_accounts_v3.getGet an AWS base accountread
  • qualys_vmdr.aws_base_accounts_v3.searchSearch AWS base accountsread
Agent binaries1
  • qualys_vmdr.agent_binaries.infoGet Cloud Agent binary informationread
Connector errors V31
  • qualys_vmdr.connector_errors_v3.searchSearch connector errorsread
Portal1
  • qualys_vmdr.portal.versionGet the Qualys portal and API versionread

Questions

The Qualys VMDR MCP server, answered.

Is there a Qualys VMDR MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 115 Qualys VMDR actions across assets, host assets, aws connectors V3 and tags, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Qualys VMDR.

What do I need to connect Qualys VMDR?

Qualys user name with API access and That user's password. Plus your host. The free call account { op: "connections.requirements", service: "qualys_vmdr" } lists exactly what to paste.

Can an AI agent delete or change things in Qualys VMDR?

Only if its key allows it, and only with an explicit confirmation. 24 Qualys VMDR actions are destructive, including delete a host asset, delete a tag and delete an asset. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my Qualys VMDR API limit?

actionlake paces every call to the limits in the Qualys VMDR service file: 300 calls an hour per connection. Repeated reads are answered from cache (40 Qualys VMDR actions can be), which never reaches Qualys VMDR.

What does a Qualys VMDR action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (115 Qualys VMDR actions page). Cache hits, searches, dry runs and calls Qualys VMDR refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Qualys VMDR API does it cover?

The Qualys Asset Management & Tagging API v2/v3 (QPS) and Cloud Agent API (QPS 1.0) at your Qualys VMDR instance's API base URL, which you enter when connecting. It is built from Qualys VMDR's documentation as read on 22 October 2026. 115 actions in 19 areas, each one in the signed service file (version 1.0.0).

Does actionlake keep my Qualys VMDR data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Qualys VMDR credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

More connectors like Qualys VMDR

Shares the most action names with

Joins with, on shared entities

Browse

actionlake is independent. It is not made or endorsed by Qualys VMDR; the name is the vendor's own. Counts are from the Qualys VMDR service file, version 1.0.0.

Give your agent Qualys VMDR today.

Connect Qualys VMDR freeSee pricing

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.