Skip to main content
Glama

Attach a resource to an app

attach_resource
Destructive

Attach a resource to an app: a named set of environment variables, such as a database's connection string, that the app reads as secrets. Publish the app first, and name the resource. When the organization has none by that name, pass a provider from list_catalog_resources and the first call creates it, returning at once with state provisioning; provisioning takes about a minute. Call again every ten seconds with the same arguments, env_prefix included, until the state is attached: the call that finds the resource ready attaches it, sets its variables, and asks for a restart if the app is running. The state is attaching while Valet still owes the restart or the variables, and conflicted when a name the resource sets is already set on the app; the answer gives the reason. An existing resource attaches by name alone, including one another app holds. One name is one resource, and an app can hold several; pass env_prefix when two would set the same variables. Pass plain_vars for plain configuration the app needs beside the database, name to value; it is readable from the dashboard, and a name or value that looks like a secret is refused. For a secret, such as an API key, pass its name in secret_names and say in reason why it is needed: the call that attaches also returns a request whose url the person opens, signed in to Valet, to enter each value; follow it with get_request, and never ask the person to type a secret into this conversation. plain_vars and secret_names apply only on the call that attaches, so repeat them on every call. A new database is empty, so the app creates its own tables, and its URL carries the TLS settings it needs. The running process sees the variables once the restart completes; get_service shows the attachment's status. Values are never returned here. Credentials in a reason read [redacted]. Requires connecting a Valet account.

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": {
      "name": "<name>",
      "resource": "<resource>"
    },
    "name": "attach_resource"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe app's name, as list_services shows it: the app to attach the resource to.
planNoThe provider's plan. Omit to use its first plan. Repeat it on every call for one resource.
reasonNoShown to the person on the request page to explain why the values are needed, so they can decide whether to enter them, such as: The app charges cards and needs your Stripe key.
org_nameNoThe Valet organization the app belongs to. Omit to use the organization the account joined first.
providerNoThe provider to create the resource from, as list_catalog_resources names it. Give it when the organization has no resource by this name.
resourceYesWhich resource the app gets, such as shop-db. A name the organization holds shares that resource with this app; a new name creates one from provider, which the organization then keeps under that name. A private system is never attached here: the call answers state requested with an access request an org Admin approves within 24 hours.
env_prefixNoSet the resource's variables under PREFIX_NAME rather than NAME, so two resources that set the same variables can both attach. Omit to use the names as they are. Repeat it on every call for one resource: it applies on the call that attaches.
plain_varsNoPlain configuration to set in the restart the attach requests, as variable name to value, such as LOG_LEVEL to debug. Readable from the dashboard: never a secret, and a name or value that looks like one is refused. Set on the call that attaches. Leave out the names the resource sets.
secret_namesNoNames of secret variables, such as STRIPE_KEY, for the person to enter on the request page. Never values. Requested on the call that attaches. Leave out the names the resource sets.

Output Schema

NameRequiredDescriptionDefault
orgYesName of the Valet organization the call acted in.
nameYesName of the app the resource is attached to.
planNoPlan the resource runs on. Absent for a resource created from environment variables.
stateYesWhere the resource or its attachment stands. provisioning: the provider is still creating the resource, so call attach_resource again. attached, attaching, conflicted, detaching, or detached: the state of the attachment to the app, with reason saying why when it is not attached or detached. requested: the resource is a private system, and an org Admin must approve the access request under request; nothing changed yet. failed: provisioning failed, and reason says why. deprovisioning or deprovisioned: the resource is being or has been removed.
reasonNoWhy a failed resource failed, as the provider said, or why the attachment is attaching, detaching, or conflicted. Absent when there is nothing to explain.
requestNoThe request a person completes in the dashboard to enter a value that must not pass through this conversation. Absent when nothing needs a person.
env_varsNoNames of the environment variables the attachment sets on the app, or a detach removed from it. Never their values.
providerNoProvider the resource was provisioned from. Absent for a resource created from environment variables.
resourceYesName of the resource in the organization. Pass it as resource to attach_resource, detach_resource, or destroy_resource.
redactionsYesHow many credentials were replaced with [redacted] in the text this answer was built from: secret values the service holds, and strings shaped like an API key, a private key, a token, or a password in a URL or header. Redaction is best effort, so 0 does not prove the text holds no credential.
resource_idNoID of the resource. Absent when the call stopped before it found or created one.
kept_env_varsNoNames of variables a detach left on the app because their values are not the ones the resource set. Absent when it kept none.
plain_vars_setNoNames of the plain_vars this call set on the app, in the restart the attach requested.
plain_vars_not_setNoNames of the plain_vars this call left unset because it did not attach the resource. Pass them again on the call that attaches.
replaced_resource_idNoID of a destroyed resource that held this name before this call provisioned a new one under it. Absent when the call replaced nothing.
secret_names_not_requestedNoNames of the secret_names this call requested no value for because it did not attach the resource. Pass them again on the call that attaches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / resource / description
      Previous value: -"Which resource the app gets, such as shop-db. A name the organization holds shares that resource with this app; a new name creates one from provider, which the organization then keeps under that name."New value: +"Which resource the app gets, such as shop-db. A name the organization holds shares that resource with this app; a new name creates one from provider, which the organization then keeps under that name. A private system is never attached here: the call answers state requested with an access request an org Admin approves within 24 hours."
    • changedOutput schema / properties / state / description
      Previous value: -"Where the resource or its attachment stands. provisioning: the provider is still creating the resource, so call attach_resource again. attached, attaching, conflicted, detaching, or detached: the state of the attachment to the app, with reason saying why when it is not attached or detached. failed: provisioning failed, and reason says why. deprovisioning or deprovisioned: the resource is being or has been removed."New value: +"Where the resource or its attachment stands. provisioning: the provider is still creating the resource, so call attach_resource again. attached, attaching, conflicted, detaching, or detached: the state of the attachment to the app, with reason saying why when it is not attached or detached. requested: the resource is a private system, and an org Admin must approve the access request under request; nothing changed yet. failed: provisioning failed, and reason says why. deprovisioning or deprovisioned: the resource is being or has been removed."
  2. Changed1 schema field changed
    • changedInput schema / properties / reason / description
      Previous value: -"Why the request is made, in words the person reads on the request page before entering anything, so they know what the values are for, such as: The app charges cards and needs your Stripe key."New value: +"Shown to the person on the request page to explain why the values are needed, so they can decide whether to enter them, such as: The app charges cards and needs your Stripe key."
  3. Changed2 schema fields changed
    • changedInput schema / properties / reason / description
      Previous value: -"Why the request is made, in the words the person reads on the request page, such as: The app charges cards and needs your Stripe key."New value: +"Why the request is made, in words the person reads on the request page before entering anything, so they know what the values are for, such as: The app charges cards and needs your Stripe key."
    • changedInput schema / properties / resource / description
      Previous value: -"The organization resource to attach, such as shop-db. A name the organization already holds attaches that resource; any other name is created from provider."New value: +"Which resource the app gets, such as shop-db. A name the organization holds shares that resource with this app; a new name creates one from provider, which the organization then keeps under that name."
  4. Changed2 schema fields changed
    • changedInput schema / properties / reason / description
      Previous value: -"Why the request is made, in the words the person reads on the request page, such as: The app charges cards and needs your Stripe key. Give it with secret_names."New value: +"Why the request is made, in the words the person reads on the request page, such as: The app charges cards and needs your Stripe key."
    • changedInput schema / properties / resource / description
      Previous value: -"The name of the organization resource to attach, such as shop-db. An existing resource attaches by name alone; a name the organization lacks is created from provider. Repeat it on every call for one resource."New value: +"The organization resource to attach, such as shop-db. A name the organization already holds attaches that resource; any other name is created from provider."
  5. Changed2 schema fields changed
    • changedInput schema / properties / reason / description
      Previous value: -"Give it with secret_names. Why the request is made, in the words the person reads on the request page, such as: The app charges cards and needs your Stripe key."New value: +"Why the request is made, in the words the person reads on the request page, such as: The app charges cards and needs your Stripe key. Give it with secret_names."
    • changedInput schema / properties / resource / description
      Previous value: -"The organization resource to attach, such as shop-db: an existing one, or a new one to provision from provider. Repeat it on every call for one resource."New value: +"The name of the organization resource to attach, such as shop-db. An existing resource attaches by name alone; a name the organization lacks is created from provider. Repeat it on every call for one resource."
  6. Changed2 schema fields changed
    • addedOutput schema / properties / redactions
      Added value: +{
      +  "description": "How many credentials were replaced with [redacted] in the text this answer was built from: secret values the service holds, and strings shaped like an API key, a private key, a token, or a password in a URL or header. Redaction is best effort, so 0 does not prove the text holds no credential.",
      +  "type": "integer"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "org",
      -  "name",
      -  "resource",
      -  "state"
      -]New value: +[
      +  "org",
      +  "name",
      +  "resource",
      +  "state",
      +  "redactions"
      +]
  7. Changed1 schema field changed
    • changedInput schema / properties / reason / description
      Previous value: -"Give it with secret_names. Why the value is needed, in the words the person reads on the request page, such as: The app charges cards and needs your Stripe key."New value: +"Give it with secret_names. Why the request is made, in the words the person reads on the request page, such as: The app charges cards and needs your Stripe key."
  8. Changed1 schema field changed
    • changedOutput schema / properties / name / description
      Previous value: -"Name of the app the resource is attached to, or was detached from."New value: +"Name of the app the resource is attached to."
  9. Changed3 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"The app's name."New value: +"The app's name, as list_services shows it: the app to attach the resource to."
    • changedInput schema / properties / reason / description
      Previous value: -"Give it with secret_names. One plain sentence, shown to the person on the request page, saying why the value is needed, such as: The app charges cards and needs your Stripe key."New value: +"Give it with secret_names. Why the value is needed, in the words the person reads on the request page, such as: The app charges cards and needs your Stripe key."
    • changedInput schema / properties / resource / description
      Previous value: -"The resource's name in the organization, such as shop-db. Repeat it on every call for one resource."New value: +"The organization resource to attach, such as shop-db: an existing one, or a new one to provision from provider. Repeat it on every call for one resource."
  10. Changed28 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"Required. The app's name."New value: +"The app's name."
    • changedInput schema / properties / plain_vars / description
      Previous value: -"Plain configuration to set in the restart the attach requests, as variable name to value, such as LOG_LEVEL to debug. Readable from the dashboard: never a secret. Set on the call that attaches. Leave out the names the resource sets."New value: +"Plain configuration to set in the restart the attach requests, as variable name to value, such as LOG_LEVEL to debug. Readable from the dashboard: never a secret, and a name or value that looks like one is refused. Set on the call that attaches. Leave out the names the resource sets."
    • changedInput schema / properties / provider / description
      Previous value: -"The provider to create the resource from, from list_catalog_resources. Required when the organization has no resource by this name."New value: +"The provider to create the resource from, as list_catalog_resources names it. Give it when the organization has no resource by this name."
    • changedInput schema / properties / reason / description
      Previous value: -"Required with secret_names. One plain sentence, shown to the person on the request page, saying why the value is needed, such as: The app charges cards and needs your Stripe key. At most 280 characters."New value: +"Give it with secret_names. One plain sentence, shown to the person on the request page, saying why the value is needed, such as: The app charges cards and needs your Stripe key."
    • changedInput schema / properties / resource / description
      Previous value: -"Required. The resource's name in the organization, such as shop-db: 3 to 63 lowercase letters, digits, and hyphens. Repeat it on every call for one resource."New value: +"The resource's name in the organization, such as shop-db. Repeat it on every call for one resource."
    • addedInput schema / properties / resource / maxLength
      Added value: +63
    • addedInput schema / properties / resource / minLength
      Added value: +3
    • addedInput schema / properties / resource / pattern
      Added value: +"^[a-z0-9][a-z0-9-]{1,61}[a-z0-9]$"
    • addedOutput schema / properties / env_vars / description
      Added value: +"Names of the environment variables the attachment sets on the app, or a detach removed from it. Never their values."
    • addedOutput schema / properties / kept_env_vars / description
      Added value: +"Names of variables a detach left on the app because their values are not the ones the resource set. Absent when it kept none."
    • addedOutput schema / properties / name / description
      Added value: +"Name of the app the resource is attached to, or was detached from."
    • addedOutput schema / properties / org / description
      Added value: +"Name of the Valet organization the call acted in."
    • addedOutput schema / properties / plain_vars_not_set / description
      Added value: +"Names of the plain_vars this call left unset because it did not attach the resource. Pass them again on the call that attaches."
    • addedOutput schema / properties / plain_vars_set / description
      Added value: +"Names of the plain_vars this call set on the app, in the restart the attach requested."
    • addedOutput schema / properties / plan / description
      Added value: +"Plan the resource runs on. Absent for a resource created from environment variables."
    • addedOutput schema / properties / provider / description
      Added value: +"Provider the resource was provisioned from. Absent for a resource created from environment variables."
    • addedOutput schema / properties / reason / description
      Added value: +"Why a failed resource failed, as the provider said, or why the attachment is attaching, detaching, or conflicted. Absent when there is nothing to explain."
    • addedOutput schema / properties / replaced_resource_id / description
      Added value: +"ID of a destroyed resource that held this name before this call provisioned a new one under it. Absent when the call replaced nothing."
    • addedOutput schema / properties / request / description
      Added value: +"The request a person completes in the dashboard to enter a value that must not pass through this conversation. Absent when nothing needs a person."
    • addedOutput schema / properties / request / properties / expires_at / description
      Added value: +"When the request expires unanswered, as an RFC 3339 UTC time."
    • addedOutput schema / properties / request / properties / fields / description
      Added value: +"Names of what the person enters, never values."
    • addedOutput schema / properties / request / properties / id / description
      Added value: +"Id of the request. Pass it to get_request to follow the request."
    • addedOutput schema / properties / request / properties / next_step / description
      Added value: +"What to do next: give the person the url, then follow the request with get_request."
    • addedOutput schema / properties / request / properties / url / description
      Added value: +"Dashboard page to give the person. They open it signed in to Valet to complete the request. It holds no credential."
    • addedOutput schema / properties / resource / description
      Added value: +"Name of the resource in the organization. Pass it as resource to attach_resource, detach_resource, or destroy_resource."
    • addedOutput schema / properties / resource_id / description
      Added value: +"ID of the resource. Absent when the call stopped before it found or created one."
    • addedOutput schema / properties / secret_names_not_requested / description
      Added value: +"Names of the secret_names this call requested no value for because it did not attach the resource. Pass them again on the call that attaches."
    • addedOutput schema / properties / state / description
      Added value: +"Where the resource or its attachment stands. provisioning: the provider is still creating the resource, so call attach_resource again. attached, attaching, conflicted, detaching, or detached: the state of the attachment to the app, with reason saying why when it is not attached or detached. failed: provisioning failed, and reason says why. deprovisioning or deprovisioned: the resource is being or has been removed."
  11. Changed12 schema fields changed
    • addedInput schema / properties / plain_vars
      Added value: +{
      +  "additionalProperties": {
      +    "type": "string"
      +  },
      +  "description": "Plain configuration to set in the restart the attach requests, as variable name to value, such as LOG_LEVEL to debug. Readable from the dashboard: never a secret. Set on the call that attaches. Leave out the names the resource sets.",
      +  "type": "object"
      +}
    • addedInput schema / properties / reason
      Added value: +{
      +  "description": "Required with secret_names. One plain sentence, shown to the person on the request page, saying why the value is needed, such as: The app charges cards and needs your Stripe key. At most 280 characters.",
      +  "maxLength": 280,
      +  "type": "string"
      +}
    • removedInput schema / properties / secret
      Removed value: -{
      -  "description": "Whether vars are stored as secrets, which are encrypted and never shown again. Omit for true; pass false for plain configuration, readable from the dashboard.",
      -  "type": "boolean"
      -}
    • addedInput schema / properties / secret_names
      Added value: +{
      +  "description": "Names of secret variables, such as STRIPE_KEY, for the person to enter on the request page. Never values. Requested on the call that attaches. Leave out the names the resource sets.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 20,
      +  "type": "array"
      +}
    • removedInput schema / properties / vars
      Removed value: -{
      -  "additionalProperties": {
      -    "type": "string"
      -  },
      -  "description": "The app's own variables to set in the restart the attach requests, as name to value. They are set on the call that attaches. Leave out the names the resource sets.",
      -  "type": "object"
      -}
    • addedOutput schema / properties / plain_vars_not_set
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": [
      +    "null",
      +    "array"
      +  ]
      +}
    • addedOutput schema / properties / plain_vars_set
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": [
      +    "null",
      +    "array"
      +  ]
      +}
    • addedOutput schema / properties / request
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "expires_at": {
      +      "type": "string"
      +    },
      +    "fields": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": [
      +        "null",
      +        "array"
      +      ]
      +    },
      +    "id": {
      +      "type": "string"
      +    },
      +    "next_step": {
      +      "type": "string"
      +    },
      +    "url": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "url",
      +    "expires_at",
      +    "fields",
      +    "next_step"
      +  ],
      +  "type": [
      +    "null",
      +    "object"
      +  ]
      +}
    • addedOutput schema / properties / secret_names_not_requested
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": [
      +    "null",
      +    "array"
      +  ]
      +}
    • removedOutput schema / properties / vars_kind
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / vars_not_set
      Removed value: -{
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": [
      -    "null",
      -    "array"
      -  ]
      -}
    • removedOutput schema / properties / vars_set
      Removed value: -{
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": [
      -    "null",
      -    "array"
      -  ]
      -}
  12. Changed2 schema fields changed
    • changedInput schema / properties / env_prefix / description
      Previous value: -"Set the resource's variables under PREFIX_NAME rather than NAME: an uppercase letter, then up to 31 uppercase letters, digits, and underscores. Omit to use the names as they are. Repeat it on every call for one resource: it applies on the call that attaches."New value: +"Set the resource's variables under PREFIX_NAME rather than NAME, so two resources that set the same variables can both attach. Omit to use the names as they are. Repeat it on every call for one resource: it applies on the call that attaches."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "env_vars": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": [
      +        "null",
      +        "array"
      +      ]
      +    },
      +    "kept_env_vars": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": [
      +        "null",
      +        "array"
      +      ]
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "org": {
      +      "type": "string"
      +    },
      +    "plan": {
      +      "type": "string"
      +    },
      +    "provider": {
      +      "type": "string"
      +    },
      +    "reason": {
      +      "type": "string"
      +    },
      +    "replaced_resource_id": {
      +      "type": "string"
      +    },
      +    "resource": {
      +      "type": "string"
      +    },
      +    "resource_id": {
      +      "type": "string"
      +    },
      +    "state": {
      +      "type": "string"
      +    },
      +    "vars_kind": {
      +      "type": "string"
      +    },
      +    "vars_not_set": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": [
      +        "null",
      +        "array"
      +      ]
      +    },
      +    "vars_set": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": [
      +        "null",
      +        "array"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "org",
      +    "name",
      +    "resource",
      +    "state"
      +  ],
      +  "type": "object"
      +}
  13. Changed2 schema fields changed
    • addedInput schema / properties / secret
      Added value: +{
      +  "description": "Whether vars are stored as secrets, which are encrypted and never shown again. Omit for true; pass false for plain configuration, readable from the dashboard.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / vars
      Added value: +{
      +  "additionalProperties": {
      +    "type": "string"
      +  },
      +  "description": "The app's own variables to set in the restart the attach requests, as name to value. They are set on the call that attaches. Leave out the names the resource sets.",
      +  "type": "object"
      +}
  14. Changed1 schema field changed
    • changedInput schema / properties / provider / description
      Previous value: -"The provider to create the resource from, from list_resource_catalog. Required when the organization has no resource by this name."New value: +"The provider to create the resource from, from list_catalog_resources. Required when the organization has no resource by this name."
  15. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (destructive, openWorld, non-idempotent), the description discloses the full state machine (provisioning, attaching, attached, conflicted, requested), the ~1 minute provisioning latency, the restart side effect on a running app, the conflict condition when a variable name is already set, and that values are never returned and credentials in a reason are redacted. It also states the auth requirement ('Requires connecting a Valet account') and the secret-entry flow that must never happen in-conversation.

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?

The purpose and preconditions are front-loaded and nearly every sentence carries operational information, including the repeated 'repeat it on every call' warnings that prevent a real failure mode. The cost is a single dense paragraph of roughly 300 words that is hard to scan; bulleted state/parameter grouping would improve it without cutting content.

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-object, stateful mutation tool, the description covers everything an agent needs: prerequisites, the create-vs-attach branch, the polling cadence and terminal states, restart implications, secret handling, and where to check status (get_service). Return values are covered by the output schema, so their absence from the description is appropriate.

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 the baseline is 3, but the description adds cross-call semantics the schema cannot express: env_prefix, plain_vars, and secret_names apply only on the attaching call and must be repeated, and provider is only needed when the org has no resource by that name. It does not discuss plan or org_name, leaving two parameters to the schema alone.

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?

The description opens with a specific verb and resource ('Attach a resource to an app') and immediately defines what a resource is ('a named set of environment variables... that the app reads as secrets'), which an agent cannot infer from the name alone. It also names the related tools (list_catalog_resources, get_request, get_service) that participate in the workflow, so the operation is distinguishable from sibling attach_* tools.

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?

It gives explicit preconditions ('Publish the app first, and name the resource'), the exact branch for creating vs. reusing a resource ('When the organization has none by that name, pass a provider'), a concrete polling protocol ('Call again every ten seconds with the same arguments'), and selection rules between plain_vars and secret_names. It also states the alternative path for private systems (state requested with an access request) rather than leaving the agent to guess.

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.

Resources