Retrieves the items in an existing list by its ID. WHEN TO USE: - To inspect the contents of a list before processing - To verify which items are in a list - To check if a list exists
AI agents call get_list 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 performs a straightforward data retrieval operation with no side effects. It queries an existing list and returns its contents without creating, modifying, deleting, or executing anything. The read-only nature and minimal blast radius (only information disclosure) justify the Read category and low severity.
From the tool's definition Tool description states it 'Retrieves the items in an existing list by its ID' and use cases emphasize inspection and verification ('inspect the contents', 'verify which items', 'check if a list exists') with no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access get_list 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 get_list:
{
"version": "1",
"default": "deny",
"tools": {
"get_list": {}
}
}get_list 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.
Retrieves the items in an existing list by its ID. WHEN TO USE: - To inspect the contents of a list before processing - To verify which items are in a list - To check if a list exists. 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 get_list: 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.
get_list 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 get_list 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 get_list. 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.
get_list 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.