StartSecurityAnalyzer
Start the Security & Compliance Analyzer to check the backup infrastructure against best practices.
This record as markdown: /tools/kid-boy-veeam-mcp-13/startsecurityanalyzer.md
What StartSecurityAnalyzer does on Veeam VBR v13 MCP Server
AI agents invoke StartSecurityAnalyzer to trigger actions in Veeam VBR v13 MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why StartSecurityAnalyzer is rated High
This tool executes an analysis operation on the backup infrastructure, which is an actionable trigger with external effects—the analyzer will scan systems and generate compliance reports. While the operation itself is non-destructive and read-focused in nature, it belongs to Execute rather than Read because it actively invokes a system process whose scope and depth depend on infrastructure state and configuration.
From the tool's definition Tool name 'StartSecurityAnalyzer' and description 'Start the Security & Compliance Analyzer to check the backup infrastructure against best practices' indicate initiation of a scanning/analysis operation that triggers external processes within the Veeam…
Attacks that exploit this kind of access
The rule that runs StartSecurityAnalyzer safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Veeam VBR v13 MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For StartSecurityAnalyzer, this is the rule to start with:
StartSecurityAnalyzer stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Veeam VBR v13 MCP Server, apply this rule, and every StartSecurityAnalyzer call is checked against it from then on.
Questions about StartSecurityAnalyzer
Start the Security & Compliance Analyzer to check the backup infrastructure against best practices. It is categorised as a Execute tool in the Veeam VBR v13 MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Veeam VBR v13 MCP Server MCP server in PolicyLayer and add a rule for StartSecurityAnalyzer: 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.
StartSecurityAnalyzer is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the StartSecurityAnalyzer 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 StartSecurityAnalyzer. 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.
StartSecurityAnalyzer 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.
More on Veeam VBR v13 MCP Server, and thousands of servers like it.
Across the catalogue