List and search Veracode application profiles
AI agents call veracode_applications 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 enables querying and listing application profiles within the Veracode security platform. These are read-only operations that retrieve information about applications without creating, modifying, deleting, or executing any actions. The blast radius of misuse is minimal—an agent could enumerate applications but cannot cause data loss, execute code, or trigger security scans.
From the tool's definition Tool performs 'List and search' operations on Veracode application profiles, which are retrieval/query operations with no modification or deletion of data.
Attacks that exploit this kind of access
List and search Veracode application profiles. 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_applications: 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_applications 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_applications 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_applications. 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_applications 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 →