Skip to main content
Glama
This connector has been deprecated

Replaced by Control Plane.

This listing has been renamed. Control Plane is now listed as com.controlplane/mcp.

It is the same server at the same endpoint (https://mcp.cpln.io/mcp), so existing connections keep working. Please use the new listing going forward.

Grant Cloud Access

grant_cloud_access
DestructiveIdempotent

Give a workload credential-free access to AWS, GCP, or Azure resources through a cloud account: ensures the workload has an identity, binds the provider access to it (policyRefs or roleName for AWS, bindings or serviceAccount for GCP, roleAssignments for Azure), and waits until the identity reports it usable (an existing roleName or serviceAccount is not checked). The cloud account must exist already (create_cloud_account and how_to_create_cloud_account, which need ?toolsets=full). Replaces this identity's existing provider configuration, so previous access can be revoked for every workload sharing the identity. No key passes through the chat.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "gvc": "<gvc>",
      "workload": "<workload>",
      "provider": "<provider>",
      "cloudAccount": "<cloudAccount>"
    },
    "name": "grant_cloud_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
awsNoWith provider aws: policyRefs or roleName, one of the two.
gcpNoWith provider gcp: bindings or serviceAccount, one of the two.
gvcYesGVC name.
orgNoOrganization slug.
azureNoWith provider azure.
providerYes
workloadYesWorkload that needs the access.
waitSecondsNoSeconds to wait on the server until the identity reports the access usable, 0 to 45. The call returns as soon as it is, or with the latest state when the time runs out. Use this instead of calling again and again.
cloudAccountYesAn existing cloud account of that provider (create_cloud_account, needs `?toolsets=full`).

Output Schema

NameRequiredDescriptionDefault
okYes
dataNoThe full result. Read this, not only the summary.
detailsNo
summaryYes
nextStepsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / azure / properties / roleAssignments / description
      Previous value: -"Roles per scope, e.g. { scope: \"/subscriptions/.../resourceGroups/RG\", roles: [\"Storage Blob Data Reader\"] }."New value: +"Roles per scope, e.g. { scope: \"/subscriptions/.../resourceGroups/RG\", roles: [\"Storage Blob Data Reader\"] }; no scope means the subscription."
    • changedInput schema / properties / azure / properties / roleAssignments / items / required
      Previous value: -[
      -  "scope",
      -  "roles"
      -]New value: +[
      +  "roles"
      +]
    • changedInput schema / properties / gcp / properties / bindings / description
      Previous value: -"Roles per resource, e.g. { resource: \"//storage.googleapis.com/projects/_/buckets/NAME\", roles: [\"roles/storage.objectViewer\"] }."New value: +"Roles per resource, e.g. { resource: \"//storage.googleapis.com/projects/_/buckets/NAME\", roles: [\"roles/storage.objectViewer\"] }; no resource means the project."
    • changedInput schema / properties / gcp / properties / bindings / items / required
      Previous value: -[
      -  "resource",
      -  "roles"
      -]New value: +[
      +  "roles"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / cloudAccount / description
      Previous value: -"An existing cloud account of that provider (create_cloud_account, full profile)."New value: +"An existing cloud account of that provider (create_cloud_account, needs `?toolsets=full`)."
    • changedInput schema / properties / gvc / description
      Previous value: -"GVC slug. If the user named none, list_resources (kind \"gvc\") and let them choose."New value: +"GVC name."
  3. Added

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations by disclosing the destructive side effect in concrete terms: "Replaces this identity's existing provider configuration, so previous access can be revoked for every workload sharing the identity." It also explains the wait semantics and the exception that an existing roleName or serviceAccount is not checked, plus the security note "No key passes through the chat."

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and mechanism, and every clause carries information (prerequisites, replacement risk, wait behavior). The opening is one very long multi-parenthetical sentence, which is dense but not padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter, nested, destructive, long-running operation with an output schema, the description supplies everything an agent needs: what it grants, prerequisites, replacement risk, wait semantics, and that no secret is exposed. Return values are correctly left to the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 89%, so the baseline is 3; the description still adds meaning by mapping provider values to their required sub-fields (policyRefs/roleName, bindings/serviceAccount, roleAssignments) and by explaining waitSeconds' role as a polling substitute. The `org` parameter and provider-specific exclusivity details remain schema-only.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — "Give a workload credential-free access to AWS, GCP, or Azure resources through a cloud account" — and enumerates the mechanism (identity, provider binding, wait for usable). It is clearly distinguishable from sibling cloud/secret tools like grant_workload_secret_access and create_cloud_account.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives prerequisites ("The cloud account must exist already") plus the sibling tools to create one and the `?toolsets=full` requirement, and tells the agent to use waitSeconds "instead of calling again and again." It does not explicitly contrast itself with grant_workload_secret_access for the credential-secret case, so a 4 rather than 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.