Lists all modules in the specified organization
AI agents call list-modules to retrieve information from Terrakube MCP Server 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 existing modules without creating, modifying, deleting, or executing any operations. It is a pure read operation that gathers information from the Terrakube infrastructure management system. The low severity reflects minimal risk even if an AI agent calls it, as it only exposes existing module metadata without enabling destructive or privileged actions.
From the tool's definition Tool name 'list-modules' and description 'Lists all modules in the specified organization' indicate a query/retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
Lists all modules in the specified organization. It is categorised as a Read tool in the Terrakube MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Terrakube MCP Server MCP server in PolicyLayer and add a rule for list-modules: 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 Terrakube MCP Server. Nothing to install.
list-modules 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-modules 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-modules. 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-modules is provided by the Terrakube MCP Server MCP server (terrakube-io/mcp-server-terrakube). 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 →