Medium Risk

upload_object_storage_bucket_certificate

Upload SSL/TLS certificate for an Object Storage bucket

How to control upload_object_storage_bucket_certificate ↓

What upload_object_storage_bucket_certificate does on Linode MCP Server

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

Medium Risk

Why upload_object_storage_bucket_certificate needs a policy

This tool uploads (creates or overwrites) an SSL/TLS certificate configuration for a bucket. This is a Write operation as it modifies bucket settings reversibly—certificates can be updated or replaced. Severity is medium because certificate misconfiguration could impact bucket security or availability, but the action itself is reversible and doesn't directly expose data or financial resources.

From the tool's definition Tool name 'upload_object_storage_bucket_certificate' and description 'Upload SSL/TLS certificate for an Object Storage bucket' indicate a create/modify operation that adds or replaces a certificate resource.

Documented attack patterns abuse exactly the kind of access upload_object_storage_bucket_certificate gives an agent:

How to control upload_object_storage_bucket_certificate

PolicyLayer is an MCP gateway — it sits between your AI agents and Linode MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for upload_object_storage_bucket_certificate:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "upload_object_storage_bucket_certificate": {
      "limits": [
        {
          "counter": "upload_object_storage_bucket_certificate_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Linode MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about upload_object_storage_bucket_certificate

What does the upload_object_storage_bucket_certificate tool do? +

Upload SSL/TLS certificate for an Object Storage bucket. It is categorised as a Write tool in the Linode 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_object_storage_bucket_certificate? +

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

What risk level is upload_object_storage_bucket_certificate? +

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

Can I rate-limit upload_object_storage_bucket_certificate? +

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

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

upload_object_storage_bucket_certificate is provided by the Linode MCP Server MCP server (takashito/linode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Linode MCP Server tool call.

Start from Linode MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

416 Linode MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.