Skip to main content
Glama
Sign In
F6 ASM MCP Server

F6 ASM MCP Server

Official
by F6-Security
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

asm_get_assets

Read-onlyIdempotent

Retrieve a company's external assets with filters for type, status, asset, software, and version, using cursor pagination to resume scans or fetch changes.

Instructions

Assets of a company: POST /api/v2/assets/updated, oldest-first, following the seqUpdate cursor across pages. Filters: type, status, asset, software, version. Returns items with complete, reason and seqUpdate; when complete is false, call again with seq_update to continue. One call stops at max_items, after ~40 s or at 1 MB of output. Without a status filter excluded assets (status 'false') are included — the perimeter is status ['confirmed', 'new']. For totals use asm_assets_summary.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company_id": "<company_id>"
    },
    "name": "asm_get_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoAsset types; empty = all. Infrastructure = domain, ip, ip_range, ssl.
assetNoExact asset values (domain, IP).
fieldsNoReturn only these fields, e.g. ['asset', 'type', 'status', 'hasIssues', 'ports'].
statusNoEmpty = all, including excluded assets ('false'). The company perimeter is ['confirmed', 'new'].
compactNoDefault true: drop heavy and repeated fields (whois/DNS of domains, discovery graph, descriptions, company fields). false returns records as the API sent them.
versionNoSoftware versions.
softwareNoSoftware names, e.g. nginx.
max_itemsNoInteger, 1-5000, default 500: stop after this many assets.
page_sizeNoRecords per API request, at most 2000. A page that times out is retried at half the size automatically.
company_idYesCompany id from asm_list_companies (field id), e.g. 3f2b6c1e-0000-4a5b-8c9d-0123456789ab.
seq_updateNoResume cursor: the seqUpdate of a previous answer of this tool with the same filters. Omit to start from the oldest record. Saved after a full walk, it returns only what changed since.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well past the annotations: it discloses the ~40 s and 1 MB stop conditions, the max_items cap, the automatic half-size retry for timed-out pages, and the difference between a fresh walk and a resumed one. The read-only/idempotent profile is already covered by annotations, and the only gap left is what the 'reason' field actually contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the endpoint and cursor semantics, then filters, then return/limit behavior, then the sibling hand-off — a sensible ordering. Some content restates the schema (the filter list, max_items) in a clipped telegraphic style that is dense but not wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return contract and does so: items carry complete, reason and seqUpdate, and complete=false signals more pages. All 11 parameters are documented in the schema and the behavioral envelope (limits, retries, perimeter) is fully stated for a paginated read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond it: the seq_update cursor only yields deltas when saved after a full walk, and a status-less call includes 'false' assets. It slightly duplicates the filter list already enumerated in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Assets of a company' via POST /api/v2/assets/updated), the ordering (oldest-first) and the traversal model (seqUpdate cursor across pages). It explicitly names asm_assets_summary as the tool for totals, so an agent can separate the two without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives the exact continuation rule ('when complete is false, call again with seq_update') and routes the aggregate case to asm_assets_summary. It also warns that omitting a status filter widens the perimeter beyond the company's ['confirmed','new'] set, which is the main way an agent could misread its own results.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools