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.

Allow Workload Access

allow_workload_access
DestructiveIdempotent

Let other workloads reach a workload inside the platform: adds the callers to what its internal firewall already admits, keeps every other firewall rule, and returns the internal URL the callers use. A caller in another GVC works by being listed. remove true takes callers off the list; a same-gvc or same-org rule still admits them. Network reach only: secret access is grant_workload_secret_access, cloud access is grant_cloud_access.

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>",
      "callers": "<callers>"
    },
    "name": "allow_workload_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
gvcYesGVC name.
orgNoOrganization slug.
removeNotrue takes the callers out of the list instead.
callersYesWorkloads that may reach it, including ones not created yet.
workloadYesWorkload to reach.

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. Changed1 schema field changed
    • 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."
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Goes beyond the annotations by explaining the mutation is additive — it appends callers to the existing firewall list and keeps every other rule — and by disclosing residual access: a same-gvc or same-org rule still admits removed callers. It does not cover permission/auth prerequisites or propagation timing, which keeps it short of a 5 despite the destructiveHint context being usefully narrowed.

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 its side effects, then the removal case, then sibling routing — a good ordering with no filler. Some sentences are telegraphic to the point of ambiguity ('A caller in another GVC works by being listed'), which costs a point.

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?

Output schema covers the returned internal URL and annotations cover safety/idempotency, so the description only needed to add mutation semantics and tool routing, which it does. Missing only authorization/prerequisite context for a cross-workload network change.

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 100% so baseline is 3, but the description adds meaning: 'A caller in another GVC works by being listed' explains why the nested gvc field is optional, and remove=true is framed as the inverse operation on the same list. It still does not address the optional 'org' parameter.

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 (let workloads reach a workload, i.e. add firewall callers) plus the concrete effect: existing rules preserved and the internal URL returned. It also explicitly separates itself from the sibling grants (grant_workload_secret_access, grant_cloud_access) so the agent can pick the right tool without opening schemas.

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?

Explicitly scopes usage to network reach and names the two alternatives for secret and cloud access with the condition that selects them. The remove=true inverse use case is also stated, so both directions of use are covered.

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.