upload_custom_certificate · CloudStack MCP Server MCP

WHAT IT DOES

What upload_custom_certificate does on CloudStack MCP Server

AI agents use upload_custom_certificate 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 upload_custom_certificate needs a policy

Uploading a custom SSL certificate modifies infrastructure configuration and can affect all encrypted communications in the CloudStack environment. While reversible (can be replaced), it impacts system-wide security posture and could enable man-in-the-middle attacks if a malicious certificate is installed.

From the tool's definition Tool name 'upload_custom_certificate' and description 'Upload a custom SSL certificate' indicate creation/modification of certificate data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

upload_custom_certificate Rate-limited

upload_custom_certificate 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": {
    "upload_custom_certificate": {
      "limits": [
        {
          "counter": "upload_custom_certificate_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 upload_custom_certificate

What does the upload_custom_certificate tool do? +

Upload a custom SSL certificate. 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 upload_custom_certificate? +

Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for upload_custom_certificate: 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 upload_custom_certificate? +

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

Can I rate-limit upload_custom_certificate? +

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

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

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