variable-list
Lists repository, organization, or environment GitHub Actions variables with values and metadata.
This record as markdown: /tools/io-github-dave-london-docker/variable-list.md
What variable-list does on Docker
AI agents call variable-list to retrieve information from Docker without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why variable-list is rated Low
This tool queries and retrieves GitHub Actions variables (credentials, configuration, secrets metadata) without creating, modifying, or deleting anything. It has no side effects and merely exposes existing data. The severity is low because while the data returned could be sensitive, the tool itself performs only read operations.
From the tool's definition Tool name 'variable-list' and description 'Lists repository, organization, or environment GitHub Actions variables with values and metadata' indicates retrieval of configuration data without modification.
Attacks that exploit this kind of access
The rule that runs variable-list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Docker, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For variable-list, this is the rule to start with:
variable-list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Docker, apply this rule, and every variable-list call is checked against it from then on.
Questions about variable-list
Lists repository, organization, or environment GitHub Actions variables with values and metadata. It is categorised as a Read tool in the Docker MCP Server, which means it retrieves data without modifying state.
Register the Docker MCP server in PolicyLayer and add a rule for variable-list: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Docker. Nothing to install.
variable-list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the variable-list rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for variable-list. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
variable-list is provided by the Docker MCP server (@paretools/docker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Docker, and thousands of servers like it.
This server
Across the catalogue