Get scan status and summary report for a Veracode application
AI agents call veracode_scan_status 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 and queries existing scan status information and summary reports from Veracode. It has no side effects, does not modify data, execute commands, delete records, or commit financial transactions. It is a straightforward Read operation that presents information to the user for review and decision-making.
From the tool's definition Tool description states 'Get scan status and summary report' — a retrieval operation with no modification, creation, deletion, or execution of code. The verb 'Get' and context of 'status' and 'report' indicate read-only querying of Veracode scan data.
Attacks that exploit this kind of access
Get scan status and summary report 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_scan_status: 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_scan_status 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_scan_status 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_scan_status. 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_scan_status 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 →