List recent catalog orders and their deployment status.
AI agents call list_catalog_orders to retrieve information from Morpheus MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query to retrieve and display historical catalog orders and their status. It has no side effects, does not create, modify, delete, or execute any resources or workflows. The blast radius of misuse is minimal—an attacker could only gain visibility into existing orders.
From the tool's definition Tool name is 'list_catalog_orders' and description states it 'List[s] recent catalog orders and their deployment status' — a retrieval operation with no modification or execution of commands.
Attacks that exploit this kind of access
List recent catalog orders and their deployment status. It is categorised as a Read tool in the Morpheus MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Morpheus MCP Server MCP server in PolicyLayer and add a rule for list_catalog_orders: 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 Morpheus MCP Server. Nothing to install.
list_catalog_orders 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_catalog_orders 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_catalog_orders. 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_catalog_orders is provided by the Morpheus MCP Server MCP server (nixndme/morpheus-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 →