get_source_details
AI agents call get_source_details 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.
The tool name and context strongly suggest this retrieves or queries information about data sources (likely port requirement sources or documentation references) without modifying, executing, or deleting anything. No side effects are implied. Confidence is moderate (0.75) rather than high because the description is empty, leaving some ambiguity about the exact operation and data sensitivity.
From the tool's definition Tool name 'get_source_details' suggests data retrieval. Server description indicates the MCP provides 'structured access' to port requirements and enables 'querying' ports.
Attacks that exploit this kind of access
get_source_details. 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_source_details: 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_source_details 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_source_details 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_source_details. 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_source_details 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 →