Modify the Security & Compliance Analyzer schedule.
AI agents use ModifySecurityAnalyzerSchedule to create or update resources in Veeam VBR v13 MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Veeam VBR v13 MCP Server environment.
This tool creates or modifies data reversibly by changing the schedule of a critical security compliance system. While not destructive (the change is reversible), it constitutes a Write action that alters system configuration.
From the tool's definition Tool name 'ModifySecurityAnalyzerSchedule' explicitly indicates modification of an existing configuration (schedule). The description states it modifies (not reads) the Security & Compliance Analyzer schedule, which is a system configuration setting.
Attacks that exploit this kind of access
Modify the Security & Compliance Analyzer schedule. It is categorised as a Write tool in the Veeam VBR v13 MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Veeam VBR v13 MCP Server MCP server in PolicyLayer and add a rule for ModifySecurityAnalyzerSchedule: 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.
ModifySecurityAnalyzerSchedule is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ModifySecurityAnalyzerSchedule 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 ModifySecurityAnalyzerSchedule. 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.
ModifySecurityAnalyzerSchedule 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 →