List all available modules that can be added to a LaunchFrame project (e.g., feature-flags, multi-tenancy).
AI agents call cli_module_list to retrieve information from LaunchFrame MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays available modules for a LaunchFrame project. It performs a simple query/list operation without creating, modifying, deleting, or executing code. The output is informational metadata about the project's module ecosystem, with no capability to alter project state or trigger external operations.
From the tool's definition Tool name 'cli_module_list' and description 'List all available modules' indicate a retrieval operation with no side effects. The verb 'list' is explicitly a read operation.
Attacks that exploit this kind of access
List all available modules that can be added to a LaunchFrame project (e.g., feature-flags, multi-tenancy). It is categorised as a Read tool in the LaunchFrame MCP MCP Server, which means it retrieves data without modifying state.
Register the LaunchFrame MCP server in PolicyLayer and add a rule for cli_module_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 LaunchFrame MCP. Nothing to install.
cli_module_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 cli_module_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 cli_module_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.
cli_module_list is provided by the LaunchFrame MCP server (launchframe-dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →