Get vulnerability findings/flaws for a Veracode application
AI agents call veracode_findings to retrieve information from MCP Veracode without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves security vulnerability data from Veracode applications. While it is fundamentally a Read operation (no data modification or deletion), the severity is elevated to medium because vulnerability findings contain sensitive security information that could be misused by a malicious agent to identify and exploit weaknesses in an organization's applications.
From the tool's definition Tool description states 'Get vulnerability findings/flaws' which is a retrieval operation with no side effects. The name and description indicate querying/fetching data about vulnerabilities.
Attacks that exploit this kind of access
Get vulnerability findings/flaws for a Veracode application. It is categorised as a Read tool in the MCP Veracode MCP Server, which means it retrieves data without modifying state.
Register the MCP Veracode MCP server in PolicyLayer and add a rule for veracode_findings: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches MCP Veracode. Nothing to install.
veracode_findings is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the veracode_findings rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for veracode_findings. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
veracode_findings is provided by the MCP Veracode MCP server (landscapedotcl/mcp-veracode). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →