list_packs
List design packs from the version library so you can pick one per site for create_sites (pass its id as packId), or browse the user's own packs ("my version library"). Filter with owner (all = official + the user's own, mine = only the user's, official = built-in only) and category (see list_pac...
This record as markdown: /tools/a3plus-mcp/list-packs.md
What list_packs does on A3plus
AI agents call list_packs to retrieve information from A3plus without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Max packs to return (default 100, max 200). |
owner | string | — | all (default) = official + your own; mine = only your packs; official = built-in only. |
category | string | — | Filter by a category id (e.g. casino, blog, restaurant). See list_pack_categories. |
Parameters from the server's own tool schema.
Why list_packs is rated Low
Even though list_packs only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs list_packs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and A3plus, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_packs, this is the rule to start with:
list_packs 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 A3plus, apply this rule, and every list_packs call is checked against it from then on.
Questions about list_packs
List design packs from the version library so you can pick one per site for create_sites (pass its id as packId), or browse the user's own packs ("my version library"). Filter with owner (all = official + the user's own, mine = only the user's, official = built-in only) and category (see list_pack_categories). Each entry has previewUrl (demo-<id>.a3plus.sogdia.market) for a live standalone preview. Vary packs across a batch so sibling sites don't look identical. It is categorised as a Read tool in the A3plus MCP Server, which means it retrieves data without modifying state.
list_packs accepts 3 parameters: limit, owner, category. The full parameter table on this page comes from the server's own tool schema.
Register the A3plus MCP server in PolicyLayer and add a rule for list_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 A3plus. Nothing to install.
list_packs 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_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.
Set action: deny in the PolicyLayer policy for list_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.
list_packs is provided by the A3plus MCP server (a3plus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on A3plus, and thousands of servers like it.
This server
Across the catalogue