Skip to main content
Glama

Runtime Correlation

runtime_correlate
Read-onlyIdempotent

Cross-references vulnerability scans with proxy runtime logs to confirm which vulnerable tools were called, and processes OTel traces for ML API call provenance.

Instructions

Cross-reference vulnerability scan results with proxy runtime audit logs.

    Identifies which vulnerable tools were ACTUALLY CALLED in production,
    distinguishing confirmed attack surface from theoretical risk. Produces
    risk-amplified findings: a vulnerable tool that was called 100 times is
    higher priority than one never invoked.

    Also accepts an OTel trace file (``otel_trace``) to extract ML API call
    provenance: which models were called, token usage, and deprecation advisories.

    Requires a proxy audit log (generated by running agent-bom proxy with
    the --log flag). Without an audit log, returns scan results only.

    Returns:
        JSON with correlated findings (CVE + tool call data + amplified risk),
        summary stats, uncalled vulnerable tools, and ml_api_calls provenance.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
config_pathNoPath to MCP config directory (e.g. ~/.config/claude) or 'auto' for default discovery.auto
audit_logNoPath to proxy audit JSONL log file (generated by 'agent-bom proxy --log audit.jsonl').
otel_traceNoPath to OTel OTLP JSON trace file for ML API provenance (detects deprecated/vulnerable model versions).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already indicate read-only, idempotent behavior. Description adds context: requires audit log, produces risk-amplified findings, and returns scan-only if no audit log. No contradictions.

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?

Description is well-structured with clear sections, front-loaded main purpose, and includes output summary. Slightly verbose but earned.

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

Completeness4/5

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

Given output schema exists, description covers purpose, prerequisites, optional features, and fallback. Could mention config_path more explicitly, but sufficient for an agent to decide.

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% with descriptions. Description adds usage context: audit_log from proxy command, otel_trace for ML provenance, and explains conditional behavior without audit log.

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?

Clearly states that the tool cross-references vulnerability scan results with proxy runtime audit logs to identify actually called vulnerable tools, distinguishing it from sibling tools like 'scan' which only performs static analysis.

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

Usage Guidelines4/5

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

Describes prerequisite of audit log from agent-bom proxy and fallback behavior. Does not explicitly compare to alternatives but implies usage after scan for runtime correlation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/msaad00/agent-bom'

If you have feedback or need assistance with the MCP directory API, please join our Discord server