AI agents call list_packs to retrieve information from Odgs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list' prefix is characteristic of retrieval operations with no side effects. Within a governance validation engine context, listing available packs is a query operation. Absence of description lowers confidence slightly, but the naming pattern and absence of write/delete/execute keywords make Read the most appropriate classification.
From the tool's definition Tool name 'list_packs' strongly suggests a read-only listing/query operation. No description provided, so relying on naming convention and context from sibling tools (download_pack, harvest_sovereign_rules) which are also non-destructive.
Attacks that exploit this kind of access
list_packs. It is categorised as a Read tool in the Odgs MCP Server, which means it retrieves data without modifying state.
Register the Odgs 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 Odgs. 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 Odgs MCP server (metricprovenance/odgs-mcp-server). 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 →