register_user_keys · CloudStack MCP Server MCP

WHAT IT DOES

What register_user_keys does on CloudStack MCP Server

AI agents use register_user_keys to create or update resources in CloudStack MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CloudStack MCP Server environment.

WHY IT NEEDS A POLICY

Why register_user_keys needs a policy

This tool creates new API credentials (key/secret pair) for a user, which is a reversible Write operation. While not destructive, it has high severity because compromised or maliciously registered API keys could grant unauthorized access to CloudStack infrastructure, and the blast radius is significant in an enterprise context. The tool modifies security state by adding new authentication material.

From the tool's definition Tool name: 'register_user_keys'; description: 'Register API key/secret key for a user'. The verb 'register' indicates creation of new authentication credentials.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

register_user_keys Rate-limited

register_user_keys 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": {
    "register_user_keys": {
      "limits": [
        {
          "counter": "register_user_keys_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 CloudStack MCP Server, so you can run agents against it safely.

FAQ

Questions about register_user_keys

What does the register_user_keys tool do? +

Register API key/secret key for a user. It is categorised as a Write tool in the CloudStack 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 register_user_keys? +

Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for register_user_keys: 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 CloudStack MCP Server. Nothing to install.

What risk level is register_user_keys? +

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

Can I rate-limit register_user_keys? +

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

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

register_user_keys is provided by the CloudStack MCP Server MCP server (mozg31337/cloudstack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.