get_enriched_ports
AI agents call get_enriched_ports to retrieve information from Veeam Ports without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve or enrich port information for Veeam products with no side effects. While the description is empty, the function name and context of sibling tools strongly suggest a data retrieval operation. Confidence is slightly reduced due to the empty description, but the pattern of other tools and server purpose make Read classification appropriate with low severity.
From the tool's definition Tool name 'get_enriched_ports' suggests retrieval of port data. Server description indicates the primary functions are 'querying ports', 'structured access', and 'search' operations.
Attacks that exploit this kind of access
get_enriched_ports. It is categorised as a Read tool in the Veeam Ports MCP Server, which means it retrieves data without modifying state.
Register the Veeam Ports MCP server in PolicyLayer and add a rule for get_enriched_ports: 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 Veeam Ports. Nothing to install.
get_enriched_ports 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 get_enriched_ports 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 get_enriched_ports. 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.
get_enriched_ports is provided by the Veeam Ports MCP server (shapedthought/veeam-ports-mcp). 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 →