Lists all existing lists and their item counts. WHEN TO USE: - To see all available lists in the current session - To find a list ID you may have forgotten - To check how many lists exist
AI agents call list_all_lists to retrieve information from Par5 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 metadata about existing lists (names and item counts) without modifying, executing, or deleting any data. It is a pure query operation used for discovery and inventory purposes, fitting clearly into the Read category with low severity since it only exposes information about the current session's state.
From the tool's definition Tool name 'list_all_lists' and description 'Lists all existing lists and their item counts' indicate a simple retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access list_all_lists gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Par5, and nothing reaches the server without passing your rules. This is the rule we recommend for list_all_lists:
{
"version": "1",
"default": "deny",
"tools": {
"list_all_lists": {}
}
} list_all_lists is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Lists all existing lists and their item counts. WHEN TO USE: - To see all available lists in the current session - To find a list ID you may have forgotten - To check how many lists exist. It is categorised as a Read tool in the Par5 MCP Server, which means it retrieves data without modifying state.
Register the Par5 MCP server in PolicyLayer and add a rule for list_all_lists: 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 Par5. Nothing to install.
list_all_lists 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_all_lists 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_all_lists. 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_all_lists is provided by the Par5 MCP server (mathematic-inc/par5-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Par5, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Par5 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.