Control Plane

Grant Workload Secret Access

grant_workload_secret_access

Destructive

Grant an EXISTING workload access to a secret: ensures it has an identity and a policy binding with reveal, and redeploys it when it is waiting on the secret. remove true revokes it, keeping the identity. Use it rather than building the identity and policy by hand. Never returns values. For a NEW workload, create_workload first; its deployment pauses on the reference until access is granted, then resumes. A missing secret: create_secret first. Does not edit env or volumes: reference the secret there as cpln://secret/NAME.KEY.

Input Schema

Name	Required	Description
`gvc`	Yes	GVC name.
`org`	No	Organization slug.
`remove`	No	true takes the secret back out of the policy instead; the identity stays.
`policyName`	No	Optional org-scoped policy resource name to create/use; pass the name only. Omit to default to {gvc}-{workloadName}-secrets-policy; another name adds a second policy for the same workload.
`secretName`	Yes	Existing org-scoped secret name to grant access to; pass the name only, not cpln://secret/... or //secret/... .
`identityName`	No	Optional identity resource name to create/use in this GVC; pass the name only. Omit to default to {gvc}-{workloadName}.
`workloadName`	Yes	Existing workload name that should receive secret access; pass the name only, not a link.

Output Schema

Name	Required	Description
`ok`	Yes
`data`	No	The full result. Read this, not only the summary.
`details`	No
`summary`	Yes
`nextSteps`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 22, 2026

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

addedInput schema / properties / remove

Added value: +{
+  "description": "true takes the secret back out of the policy instead; the identity stays.",
+  "type": "boolean"
+}

Changed31 schema fields changedSep 30, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / gvc / description

Previous value: -"GVC slug (lowercase kebab-case). Use the GVC the user named; otherwise discover with list_resources (kind=\"gvc\") and let them choose — never guess (a wrong GVC targets the wrong environment)."New value: +"GVC slug. If the user named none, list_resources (kind \"gvc\") and let them choose."

removedInput schema / properties / gvc / maxLength
```
Removed value: -63
```
removedInput schema / properties / gvc / minLength
```
Removed value: -1
```

removedInput schema / properties / gvc / pattern

Removed value: -"^[a-z0-9]([a-z0-9-]{0,61}[a-z0-9])?$"

removedInput schema / properties / identityName / maxLength
```
Removed value: -64
```
removedInput schema / properties / identityName / minLength
```
Removed value: -2
```
removedInput schema / properties / identityName / pattern
```
Removed value: -"^[a-z]([-a-z0-9])*[a-z0-9]$"
```

changedInput schema / properties / org / description

Previous value: -"Organization slug (lowercase kebab-case). NEVER guess — if the user has not named one, ask. On org-not-found, stop and ask; do not retry variants."New value: +"Organization slug."

removedInput schema / properties / org / maxLength
```
Removed value: -63
```
removedInput schema / properties / org / minLength
```
Removed value: -1
```

removedInput schema / properties / org / pattern

Removed value: -"^[a-z0-9]([a-z0-9-]{0,61}[a-z0-9])?$"

changedInput schema / properties / policyName / description

Previous value: -"Optional org-scoped policy resource name to create/use; pass the name only. Omit to default to {gvc}-{workloadName}-secrets-policy."New value: +"Optional org-scoped policy resource name to create/use; pass the name only. Omit to default to {gvc}-{workloadName}-secrets-policy; another name adds a second policy for the same workload."

removedInput schema / properties / policyName / maxLength
```
Removed value: -64
```
removedInput schema / properties / policyName / minLength
```
Removed value: -2
```
removedInput schema / properties / policyName / pattern
```
Removed value: -"^[a-z]([-a-z0-9])*[a-z0-9]$"
```
removedInput schema / properties / secretName / maxLength
```
Removed value: -64
```
removedInput schema / properties / secretName / minLength
```
Removed value: -2
```
removedInput schema / properties / secretName / pattern
```
Removed value: -"^[a-z]([-a-z0-9])*[a-z0-9]$"
```
removedInput schema / properties / workloadName / maxLength
```
Removed value: -64
```
removedInput schema / properties / workloadName / minLength
```
Removed value: -2
```
removedInput schema / properties / workloadName / pattern
```
Removed value: -"^[a-z]([-a-z0-9])*[a-z0-9]$"
```

changedInput schema / required

Previous value: -[
-  "org",
-  "gvc",
-  "workloadName",
-  "secretName"
-]New value: +[
+  "gvc",
+  "workloadName",
+  "secretName"
+]

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedOutput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / properties / data / description

Previous value: -"The full machine-readable result — list rows, the resource object, query results. Read THIS, not just the summary."New value: +"The full result. Read this, not only the summary."

addedOutput schema / properties / details
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / nextSteps / description

Removed value: -"Recommended follow-up actions for this task, in order."

removedOutput schema / properties / ok / description
```
Removed value: -"Whether the call succeeded."
```
removedOutput schema / properties / summary / description
```
Removed value: -"One-line summary of the result."
```

AddedAug 14, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only flag destructive/not-idempotent; the description goes much further by disclosing that granting creates an identity and policy binding, that redeployment is triggered when the workload waits on the secret, that revocation preserves the identity, and that deployment pauses then resumes on new workloads. 'Never returns values' also sets a security expectation about the response.

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?

Purpose leads, then alternatives, then constraints, with no filler sentences. The telegraphic semicolon-heavy packing of four distinct instructions into the middle makes it slightly dense but nothing is wasted.

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?

Given an output schema, full annotation set, and 100% parameter coverage, the description fills the remaining gaps an agent needs: prerequisites (existing workload, existing secret), ordering with create_workload/create_secret, side effects, and the env/volume boundary.

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

Parameters3/5

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

Schema coverage is 100%, so defaults such as the {gvc}-{workloadName}-secrets-policy name and the name-only convention are already documented in the schema. The description only restates remove-true semantics, which the schema parameter description already covers; the one genuine addition is the cpln://secret/NAME.KEY reference format, which is tangential to the tool's own parameters.

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 precise verb+resource pair ('grant an EXISTING workload access to a secret') and enumerates the concrete side effects (identity creation, policy binding with reveal, conditional redeploy). It also disambiguates the reverse operation ('remove true revokes it, keeping the identity') so the tool cannot be confused with allow_workload_access or grant_cloud_access.

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

Usage Guidelines5/5

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

Explicit routing instructions for every adjacent case: 'Use it rather than building the identity and policy by hand', 'For a NEW workload, create_workload first', 'A missing secret: create_secret first'. It also states a negative boundary ('Does not edit env or volumes') with the alternative mechanism (cpln://secret/NAME.KEY).

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

All Control Plane tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.