Ibmcloud

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

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

Last updated:

35 can modify or destroy data
53 read-only
88 tools total
Read (53) Write / Execute (28) Destructive / Financial (7)

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.

One command. Full control.

Intercept sits between your agent and Ibmcloud. Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.

npx -y @policylayer/intercept scan -- npx -y @ibmcloud-mcp-server
Scans every tool. Generates a policy. Starts enforcing.
Works with Claude Code · Cursor · Claude Desktop · Windsurf · any MCP client
Deny destructive operations
ibmcloud_cf_delete:
  rules:
    - action: deny

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

Rate limit write operations
ibmcloud_api:
  rules:
    - rate_limit: 30/hour

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
ibmcloud_account_list:
  rules:
    - rate_limit: 60/minute

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

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
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. Intercept 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 rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.

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 add Intercept to my Ibmcloud setup? +

One line change. Instead of running the Ibmcloud server directly, prefix it with Intercept: intercept -c io-github-expertvagabond-ibmcloud.yaml -- npx -y @ibmcloud-mcp-server. Download a pre-built policy from policylayer.com/policies/io-github-expertvagabond-ibmcloud and adjust the limits to match your use case.

Other MCP servers with similar tools.

Starter policies available for each. Same risk classification, same one-command setup.

policylayer/intercept

Control every MCP tool call
your agent makes.

Set budgets, approvals, and hard limits across MCP servers.

npx -y @policylayer/intercept init
Protect your agent in 30 seconds. Scans your MCP config and generates enforcement policies for every server.
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.