Get event forwarding settings (SNMP, syslog, etc.).
AI agents call GetEventForwardingSettings to retrieve information from Veeam VBR v13 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing event forwarding configuration metadata. Reading backup system settings poses minimal risk—it does not modify infrastructure, execute commands, delete data, or move money. The blast radius of misuse is limited to information disclosure about how the system forwards monitoring events.
From the tool's definition Tool name 'Get' and description 'Get event forwarding settings' indicate a retrieval operation with no modification. The tool queries configuration settings (SNMP, syslog) without side effects.
Attacks that exploit this kind of access
Get event forwarding settings (SNMP, syslog, etc.). It is categorised as a Read tool in the Veeam VBR v13 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Veeam VBR v13 MCP Server MCP server in PolicyLayer and add a rule for GetEventForwardingSettings: 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 VBR v13 MCP Server. Nothing to install.
GetEventForwardingSettings 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 GetEventForwardingSettings 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 GetEventForwardingSettings. 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.
GetEventForwardingSettings is provided by the Veeam VBR v13 MCP Server MCP server (kid-boy/veeam-mcp-13). 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 →