variable-list
Lists repository, organization, or environment GitHub Actions variables with values and metadata.
This record as markdown: /tools/io-github-dave-london-build/variable-list.md
What variable-list does on Build
AI agents call variable-list to retrieve information from Build 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 is a read-only tool that queries and retrieves GitHub Actions variable information. While variables may contain sensitive data (which warrants the 'low' severity), the tool itself performs no destructive, write, or execution operations. It only enumerates existing variables without side effects.
From the tool's definition Tool lists GitHub Actions variables with their values and metadata. The description uses 'Lists' and retrieves information without modifying, creating, or deleting any resources.
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 Build, 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 Build, 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 Build MCP Server, which means it retrieves data without modifying state.
Register the Build 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 Build. 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 Build MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Build, and thousands of servers like it.
This server
Across the catalogue