Critical Risk →

ibmcloud_cr_image_rm

Remove a container image

Part of the Ibmcloud server.

ibmcloud_cr_image_rm can permanently delete data in Ibmcloud, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE IBMCLOUD →

Free to start. No card required.

AI agents may call ibmcloud_cr_image_rm to permanently remove or destroy resources in Ibmcloud. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call ibmcloud_cr_image_rm in a loop, permanently destroying resources in Ibmcloud. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "ibmcloud_cr_image_rm"
  ]
}

See the full Ibmcloud policy for all 88 tools.

Get this rule live on your own Ibmcloud server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY IBMCLOUD →

View all 88 tools →

These attack patterns abuse exactly the kind of access ibmcloud_cr_image_rm gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so ibmcloud_cr_image_rm only ever does what you allow.

SECURE IBMCLOUD →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the ibmcloud_cr_image_rm tool do? +

Remove a container image. It is categorised as a Destructive tool in the Ibmcloud MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on ibmcloud_cr_image_rm? +

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

What risk level is ibmcloud_cr_image_rm? +

ibmcloud_cr_image_rm is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit ibmcloud_cr_image_rm? +

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

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

ibmcloud_cr_image_rm is provided by the Ibmcloud MCP server (ibmcloud-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 Ibmcloud tool call.

Deterministic rules across all 88 Ibmcloud tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.