Get the NestJS module folder structure, conventions, and rules used in LaunchFrame.
AI agents call module_get_structure 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 queries project-specific structural information and conventions. It has no side effects, does not modify data, execute code, delete resources, or move money. It is a read-only informational tool that returns architectural metadata to help agents understand and maintain consistency in code structure.
From the tool's definition Tool name 'module_get_structure' uses 'get' verb and description states 'Get the NestJS module folder structure, conventions, and rules' — retrieval of architectural/structural information with no modification or execution.
Attacks that exploit this kind of access
Get the NestJS module folder structure, conventions, and rules used in LaunchFrame. 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 module_get_structure: 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.
module_get_structure 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 module_get_structure 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 module_get_structure. 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.
module_get_structure 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 →