AI agents call list_models to retrieve information from Peecai without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a simple enumeration/query operation that retrieves information about available models without creating, modifying, deleting, or executing any actions. The deprecation note and reference to a newer alternative confirm this is a passive read operation. No side effects, no data manipulation, no code execution.
From the tool's definition Tool 'list_models' returns model IDs and active status with no modification capability. The verb 'list' and the description 'Returns' indicate a retrieval-only operation.
Attacks that exploit this kind of access
Deprecated: use list_model_channels instead. Model channels are stable identifiers (e.g. openai-0, perplexity-0) that persist when underlying models rotate. Returns model IDs and active status. It is categorised as a Read tool in the Peecai MCP Server, which means it retrieves data without modifying state.
Register the Peecai MCP server in PolicyLayer and add a rule for list_models: 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 Peecai. Nothing to install.
list_models 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_models 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_models. 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_models is provided by the Peecai MCP server (mcp-server-peecai). 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 →