CreateSuspiciousActivityEvent · Veeam VBR v13 MCP Server MCP

WHAT IT DOES

What CreateSuspiciousActivityEvent does on Veeam VBR v13 MCP Server

AI agents use CreateSuspiciousActivityEvent 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.

WHY IT NEEDS A POLICY

Why CreateSuspiciousActivityEvent needs a policy

This tool creates new entries in a security event log, which is a write operation that modifies system state. However, it does not irreversibly delete data (not Destructive), execute arbitrary code (not Execute), move money (not Financial), or merely retrieve data (not Read).

From the tool's definition Tool is named 'CreateSuspiciousActivityEvent' and described as 'Create a manual malware event entry.' The verb 'Create' indicates data modification; the description specifies creation of a malware event entry in what is a backup/replication system's audit or…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

CreateSuspiciousActivityEvent Rate-limited

CreateSuspiciousActivityEvent stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "CreateSuspiciousActivityEvent": {
      "limits": [
        {
          "counter": "createsuspiciousactivityevent_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Veeam VBR v13 MCP Server, so you can run agents against it safely.

FAQ

Questions about CreateSuspiciousActivityEvent

What does the CreateSuspiciousActivityEvent tool do? +

Create a manual malware event entry. 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.

How do I enforce a policy on CreateSuspiciousActivityEvent? +

Register the Veeam VBR v13 MCP Server MCP server in PolicyLayer and add a rule for CreateSuspiciousActivityEvent: 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.

What risk level is CreateSuspiciousActivityEvent? +

CreateSuspiciousActivityEvent is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit CreateSuspiciousActivityEvent? +

Yes. Add a rate_limit block to the CreateSuspiciousActivityEvent 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.

How do I block CreateSuspiciousActivityEvent completely? +

Set action: deny in the PolicyLayer policy for CreateSuspiciousActivityEvent. 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.

What MCP server provides CreateSuspiciousActivityEvent? +

CreateSuspiciousActivityEvent 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.