AI agents call list_lists to retrieve information from Pantrist without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about the user's shopping lists and pantries without modifying, executing, or destructing any data. It is a simple query operation with no side effects, fitting the Read category. Severity is low because the information returned is user-specific pantry metadata with minimal blast radius if misused by an agent.
From the tool's definition Tool description states 'Read-only' and 'List the shopping lists / pantries the authenticated user can access.' The verb 'list' and explicit 'read-only' designation confirm retrieval without side effects.
Attacks that exploit this kind of access
List the shopping lists / pantries the authenticated user can access. Read-only. Returns an array of list objects each with. It is categorised as a Read tool in the Pantrist MCP Server, which means it retrieves data without modifying state.
Register the Pantrist MCP server in PolicyLayer and add a rule for list_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 Pantrist. Nothing to install.
list_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_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_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_lists is provided by the Pantrist MCP server (pantrist-dev/pantrist-mcp). 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 →