Control Plane

Create a Policy

create_policy

Create a new policy with target kind, optional target scopes (targetAll/targetLinks/targetQuery), and principal bindings (addPermissions plus at least one principal list — one without the other is an error). Target scopes may be combined; targetAll wins because target="all" applies the policy to every resource.

Input Schema

TableJSON Schema

Name	Required	Description
`org`	No	Organization slug.
`name`	Yes	Resource name. Immutable: renaming is delete and recreate.
`tags`	No	Optional tags for the policy (behave like Kubernetes labels for selectors and compliance).
`addUsers`	No	User links to add (e.g., ["//user/alice"])
`addGroups`	No	Group links to add
`targetAll`	No	Set to true to target all resources of the kind. Pick the target scope that matches intent (combining scopes is legal; target=all wins).
`targetKind`	Yes	Target resource kind (e.g., "secret", "workload", "identity"). Only the kinds listed by get_permissions have meaningful permission schemas — confirm permission names there before binding.
`description`	No	Policy description
`targetLinks`	No	Target resource links (e.g., ["//secret/my-secret"]). GVC-scoped kinds (workload/identity/volumeset/dbcluster) need the gvc segment: //gvc/GVC/workload/NAME. Pick the target scope that matches intent (combining scopes is legal; target=all wins).
`targetQuery`	No	Dynamically target resources matching a query (e.g. all secrets tagged env=prod). Pick the target scope that matches intent (combining scopes is legal; target=all wins).
`addIdentities`	No	Identity links to add (e.g., ["//gvc/my-gvc/identity/my-identity"]). Identities are GVC-scoped — the gvc segment is required.
`addPermissions`	No	Permissions to grant (e.g., ["reveal", "use"]). For the full list run get_permissions. Secret values need `reveal`, not `read`.
`addServiceAccounts`	No	Service account links to add (e.g., ["//serviceaccount/sa-1"])

Output Schema

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

Changed34 schema fields changedSep 30, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / addGroups / maxItems
```
Removed value: -200
```
- removedInput schema / properties / addIdentities / items / pattern
```
Removed value: -"^(\\/\\/gvc\\/[^/]+\\/identity\\/[^/]+|\\/org\\/[^/]+\\/gvc\\/[^/]+\\/identity\\/[^/]+)$"
```
- removedInput schema / properties / addIdentities / maxItems
```
Removed value: -200
```
- removedInput schema / properties / addServiceAccounts / maxItems
```
Removed value: -200
```
- removedInput schema / properties / addUsers / maxItems
```
Removed value: -200
```
- removedInput schema / properties / description / maxLength
```
Removed value: -250
```
- changedInput schema / properties / name / description
```
Previous value: -"Resource name (lowercase kebab-case, starts with a letter, 2-64 chars). Names are IMMUTABLE — renaming = delete + recreate (loses URL, DNS, policy links)."New value: +"Resource name. Immutable: renaming is delete and recreate."
```
- removedInput schema / properties / name / maxLength
```
Removed value: -64
```
- removedInput schema / properties / name / minLength
```
Removed value: -2
```
- removedInput schema / properties / name / 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])?$"
```
- removedInput schema / properties / tags / items / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / tags / items / properties / key / minLength
```
Removed value: -1
```
- removedInput schema / properties / tags / maxItems
```
Removed value: -50
```
- removedInput schema / properties / targetLinks / maxItems
```
Removed value: -200
```
- removedInput schema / properties / targetQuery / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / targetQuery / properties / kind / minLength
```
Removed value: -1
```
- removedInput schema / properties / targetQuery / properties / spec / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / targetQuery / properties / spec / properties / sort / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / targetQuery / properties / spec / properties / sort / properties / by / minLength
```
Removed value: -1
```
- removedInput schema / properties / targetQuery / properties / spec / properties / terms / items / additionalProperties
```
Removed value: -false
```
- changedInput schema / required
```
Previous value: -[
-  "org",
-  "name",
-  "targetKind"
-]New value: +[
+  "name",
+  "targetKind"
+]
```
- 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."
```
First observedJun 28, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations establish the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds genuine value beyond that: the validation constraint that permissions and principals must be supplied together, and the precedence behavior where targetAll wins over other scopes. Return format is not discussed, but that is acceptable.

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

Conciseness5/5

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

Two tight sentences with zero filler, front-loading the create action and its required structure before the combination rules. Every clause carries distinct information (scope names, principal binding rule, precedence rule).

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

Completeness4/5

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

With 13 parameters, nested query objects, and an output schema present, the description covers the highest-risk interactions: scope combination, targetAll precedence, and the permissions/principals coupling. Fields like org, tags, and description are left to the schema, which is appropriate. It is complete enough to call correctly.

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 description coverage is 100%, so a baseline of 3 is warranted. The description nonetheless adds semantics the schema only implies: that the three target scopes can be legally combined and that targetAll takes precedence, plus the required coupling of addPermissions with a principal list. That is real meaning beyond the field docs.

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

Purpose4/5

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

States a specific verb (create) and resource (policy) and enumerates the compositional parts: target kind, target scopes, and principal bindings. An agent immediately knows what is being built. It stops short of naming the update_policy sibling to differentiate create-vs-modify, which keeps it at 4 rather than 5.

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 concrete operational rules: addPermissions requires at least one principal list, and combining that pair incorrectly is an error. It also explains target scope combination and the targetAll precedence rule. It does not route between create_policy and update_policy or state prerequisites like confirming permission names, so it is clear context without explicit alternatives.

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.