GetCreds

Get a specific credentials record by ID.

SERVERVeeam VBR v13 MCP Server SOURCEkid-boy/veeam-mcp-13

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kid-boy-veeam-mcp-13/getcreds.md

WHAT IT DOES

What GetCreds does on Veeam VBR v13 MCP Server

AI agents call GetCreds to retrieve information from Veeam VBR v13 MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why GetCreds is rated Low

This is a Read operation as it retrieves stored credentials. However, severity is elevated to 'high' rather than 'low' because credentials are sensitive security material: if an AI agent retrieves credentials via this tool, it could expose authentication secrets (passwords, API keys, tokens) that enable lateral movement, unauthorized access to backup systems, or compromise of protected infrastructure.

From the tool's definition Tool named 'GetCreds' and described as 'Get a specific credentials record by ID' — retrieves credential data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs GetCreds 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 GetCreds, this is the rule to start with:

GetCreds Allowed

GetCreds is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "GetCreds": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Veeam VBR v13 MCP Server, apply this rule, and every GetCreds call is checked against it from then on.

FAQ

Questions about GetCreds

What does the GetCreds tool do? +

Get a specific credentials record by ID. It is categorised as a Read tool in the Veeam VBR v13 MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on GetCreds? +

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

GetCreds is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit GetCreds? +

Yes. Add a rate_limit block to the GetCreds 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 GetCreds completely? +

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

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

KEEP EXPLORING

More on Veeam VBR v13 MCP Server, and thousands of servers like it.

This server

All 328 Veeam VBR v13 MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →