List every group and its tier counts.
AI agents call catalog_list_groups to retrieve information from tin-canMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates catalog group information and their tier counts. It is a pure read operation with no side effects, no code execution, no data modification, and no destructive actions. The blast radius of misuse is minimal—an agent could only enumerate groups and tier information already accessible through the catalog system.
From the tool's definition Tool name 'catalog_list_groups' and description 'List every group and its tier counts' indicate a retrieval operation that queries metadata without modifying, executing, or deleting anything.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List every group and its tier counts. It is categorised as a Read tool in the tin-canMCP MCP Server, which means it retrieves data without modifying state.
Register the tin-can MCP server in PolicyLayer and add a rule for catalog_list_groups: 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 tin-canMCP. Nothing to install.
catalog_list_groups 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 catalog_list_groups 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 catalog_list_groups. 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.
catalog_list_groups is provided by the tin-can MCP server (juangrukat/tin-canmcp). 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 →