list_module_packs

List DLC-like AirMCP module packs and whether each pack is available in the current runtime configuration.

SERVERIconnect SOURCEiconnect-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-heznpc-iconnect/list-module-packs.md

WHAT IT DOES

What list_module_packs does on Iconnect

AI agents call list_module_packs to retrieve information from Iconnect without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_module_packs is rated Low

This tool retrieves and queries configuration information about available modules. It has no side effects, does not execute code, does not modify data, and does not delete or move resources. It is a simple enumeration/inventory operation, making it a Read category tool.

From the tool's definition The tool 'list_module_packs' returns a list of available module packs and their availability status. The verb 'list' and description 'List DLC-like AirMCP module packs' indicate a read-only query operation with no modification of state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_module_packs safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_module_packs, this is the rule to start with:

list_module_packs Allowed

list_module_packs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_module_packs": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every list_module_packs call is checked against it from then on.

FAQ

Questions about list_module_packs

What does the list_module_packs tool do? +

List DLC-like AirMCP module packs and whether each pack is available in the current runtime configuration. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_module_packs? +

Register the Iconnect MCP server in PolicyLayer and add a rule for list_module_packs: 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 Iconnect. Nothing to install.

What risk level is list_module_packs? +

list_module_packs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_module_packs? +

Yes. Add a rate_limit block to the list_module_packs 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.

How do I block list_module_packs completely? +

Set action: deny in the PolicyLayer policy for list_module_packs. 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.

What MCP server provides list_module_packs? +

list_module_packs is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Iconnect, and thousands of servers like it.

This server

All 297 Iconnect tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →