list_component_buttons
List the [Button]-attributed methods on a component. NOTE: this only finds methods decorated with [Button]; invoke_button can ALSO call any plain public no-arg method by name, so a method missing here may still be invokable. Use describe_type / get_method_signature to find non-button methods.
This record as markdown: /tools/sbox/list-component-buttons.md
What list_component_buttons does on Sbox
AI agents call list_component_buttons to retrieve information from Sbox without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_component_buttons is rated Low
This tool purely retrieves metadata about available button methods on a component. It has no side effects—it only lists/queries existing data. While the sibling tool 'invoke_button' would execute actions, this tool merely enumerates them. This is a classic Read operation (search/list pattern).
From the tool's definition Tool name is 'list_component_buttons' and description states it 'List[s]' methods, indicating query/retrieval functionality with no modification or execution. The note clarifies this is a discovery tool for finding decorated methods, not invoking them.
Attacks that exploit this kind of access
The rule that runs list_component_buttons safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sbox, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_component_buttons, this is the rule to start with:
list_component_buttons 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 Sbox, apply this rule, and every list_component_buttons call is checked against it from then on.
Questions about list_component_buttons
List the [Button]-attributed methods on a component. NOTE: this only finds methods decorated with [Button]; invoke_button can ALSO call any plain public no-arg method by name, so a method missing here may still be invokable. Use describe_type / get_method_signature to find non-button methods. It is categorised as a Read tool in the Sbox MCP Server, which means it retrieves data without modifying state.
Register the Sbox MCP server in PolicyLayer and add a rule for list_component_buttons: 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 Sbox. Nothing to install.
list_component_buttons 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 list_component_buttons 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 list_component_buttons. 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.
list_component_buttons is provided by the Sbox MCP server (sbox-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sbox, and thousands of servers like it.
This server
Across the catalogue