// SCAN REPORT

Ibmcloud

88 tools. 35 can modify or destroy data without limits.

7 destructive tools with no built-in limits. Policy required.

Last updated: 5 Jun 2026

35 can modify or destroy data

53 read-only

88 tools total

Free to start. No card required.

TOOL MAP

Read (53) Write / Execute (28) Destructive / Financial (7)

CONTEXT-WINDOW COST

4,844 tokens of tool definitions, loaded on every request

2.4% of a 200k context window

141 heaviest tool: ibmcloud_ks_cluster_create

Full per-tool breakdown → Model it in the token calculator →

WHAT CAN GO WRONG

Destructive tools (ibmcloud_cf_delete, ibmcloud_cr_image_rm, ibmcloud_iam_api_key_delete) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.

Write operations (ibmcloud_api, ibmcloud_cf_create_service, ibmcloud_cf_push) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

Execute tools (ibmcloud_cf_restart, ibmcloud_cf_scale, ibmcloud_cf_start) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.

RECOMMENDED RULES

Deny destructive operations

{
  "ibmcloud_cf_delete": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "ibmcloud_api": {
    "limits": [
      {
        "counter": "ibmcloud_api_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "ibmcloud_account_list": {
    "limits": [
      {
        "counter": "ibmcloud_account_list_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

ALL 88 IBMCLOUD TOOLS

DESTRUCTIVE 7 tools

Destructive ibmcloud_cf_delete Destructive ibmcloud_cr_image_rm Destructive ibmcloud_iam_api_key_delete Destructive ibmcloud_iam_service_id_delete Destructive ibmcloud_ks_cluster_delete Destructive ibmcloud_resource_service_instance_delete Destructive ibmcloud_resource_service_key_delete

EXECUTE 4 tools

Execute ibmcloud_cf_restart Execute ibmcloud_cf_scale Execute ibmcloud_cf_start Execute ibmcloud_cf_stop

WRITE 24 tools

READ 53 tools

Read ibmcloud_account_list Read ibmcloud_account_show Read ibmcloud_billing_account_usage Read ibmcloud_billing_org_usage Read ibmcloud_billing_resource_group_usage Read ibmcloud_billing_resource_instances_usage Read ibmcloud_catalog_search Read ibmcloud_catalog_service Read ibmcloud_catalog_service_plans Read ibmcloud_cf_app Read ibmcloud_cf_apps Read ibmcloud_cf_bind_service Read ibmcloud_cf_env Read ibmcloud_cf_logs Read ibmcloud_cf_marketplace Read ibmcloud_cf_orgs Read ibmcloud_cf_routes Read ibmcloud_cf_services Read ibmcloud_cf_spaces Read ibmcloud_cf_unbind_service Read ibmcloud_config_list Read ibmcloud_cr_images Read ibmcloud_cr_namespaces Read ibmcloud_cr_quota Read ibmcloud_iam_access_group Read ibmcloud_iam_access_group_policies Read ibmcloud_iam_access_group_users Read ibmcloud_iam_access_groups Read ibmcloud_iam_api_keys Read ibmcloud_iam_roles Read ibmcloud_iam_service_api_keys Read ibmcloud_iam_service_id Read ibmcloud_iam_service_ids Read ibmcloud_iam_users Read ibmcloud_ks_cluster Read ibmcloud_ks_clusters Read ibmcloud_ks_flavors Read ibmcloud_ks_versions Read ibmcloud_ks_worker_pools Read ibmcloud_ks_workers Read ibmcloud_ks_zones Read ibmcloud_logout Read ibmcloud_plugin_list Read ibmcloud_plugin_repo_plugins Read ibmcloud_regions Read ibmcloud_resource_groups Read ibmcloud_resource_search Read ibmcloud_resource_service_instance Read ibmcloud_resource_service_instances Read ibmcloud_resource_service_key Read ibmcloud_resource_service_keys Read ibmcloud_resource_tags Read ibmcloud_version

FAQ

Can an AI agent delete data through the Ibmcloud MCP server? +

Yes. The Ibmcloud server exposes 7 destructive tools including ibmcloud_cf_delete, ibmcloud_cr_image_rm, ibmcloud_iam_api_key_delete. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Ibmcloud? +

The Ibmcloud server has 24 write tools including ibmcloud_api, ibmcloud_cf_create_service, ibmcloud_cf_push. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Ibmcloud.

How many tools does the Ibmcloud MCP server expose? +

88 tools across 4 categories: Destructive, Execute, Read, Write. 53 are read-only. 35 can modify, create, or delete data.

How do I enforce a policy on Ibmcloud? +

Register the Ibmcloud MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

// RELATED SERVERS

Other MCP servers with similar tools.

Starter policies for each. Same risk classification, live on your fleet in minutes.

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.

SECURE IBMCLOUD →

Free to start. No card required.

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

Ibmcloud

// TOOL MAP

// CONTEXT-WINDOW COST

// WHAT CAN GO WRONG

// RECOMMENDED RULES

// ALL 88 IBMCLOUD TOOLS

// FAQ