MCP Veracode

veracode_findings

Retrieve vulnerability findings for Veracode applications to identify security flaws, filter by severity, scan type, and policy violations for effective security analysis.

Instructions

Get vulnerability findings/flaws for a Veracode application

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": {
      "applicationGuid": "<applicationGuid>"
    },
    "name": "veracode_findings"
  }
}

Input Schema

Name	Required	Description
`applicationGuid`	Yes	Application GUID
`scanType`	No	Filter by scan type (SCA must be queried alone)
`severity`	No	Exact severity level (0-5)
`severityGte`	No	Minimum severity level (0-5)
`violatesPolicy`	No	Only findings that violate policy
`cwe`	No	Filter by CWE ID
`newFindings`	No	Only newly discovered findings
`page`	No	Page number (0-indexed)
`size`	No	Page size

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Feb 19, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read operation ('Get') but doesn't specify if it's paginated (though parameters suggest it), rate-limited, requires authentication, or what the output format is. This is a significant gap for a tool with 9 parameters and no output schema, making it inadequate for safe and effective use.

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

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it easy to parse quickly.

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

Completeness2/5

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

Given the complexity (9 parameters, no annotations, no output schema), the description is incomplete. It doesn't address behavioral aspects like pagination, error handling, or output structure, which are critical for a data retrieval tool. The high parameter count and lack of structured support make this description insufficient for reliable agent use.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema fully documents all 9 parameters. The description adds no additional meaning beyond the schema, such as explaining interactions between parameters (e.g., 'severity' vs. 'severityGte') or usage notes. This meets the baseline for high schema coverage but doesn't enhance understanding.

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

Purpose4/5

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

The description clearly states the verb ('Get') and resource ('vulnerability findings/flaws for a Veracode application'), making the purpose specific and understandable. However, it doesn't differentiate from sibling tools like 'veracode_policy_compliance' or 'veracode_scan_status' which might also relate to findings or application data.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'veracode_applications' or 'veracode_policy_compliance'. It lacks context about prerequisites, such as needing an application GUID, or exclusions, like not using it for compliance checks. This leaves the agent with minimal usage direction.

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

Deploy Server