List all cases in the project. Returns all cases with their status, useful for finding past work or setting an active case.
AI agents call list_cases to retrieve information from Decision OS MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing case data without creating, modifying, deleting, or executing operations. It is purely informational, allowing users to view past cases and their statuses. No data is changed, no code is executed, and no irreversible actions occur. This is a clear Read category operation with minimal risk if misused by an AI agent—it can only expose information already in the system.
From the tool's definition Tool name is 'list_cases' and description states it 'List all cases in the project' and 'Returns all cases with their status'. The verb 'list' and 'returns' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
List all cases in the project. Returns all cases with their status, useful for finding past work or setting an active case. It is categorised as a Read tool in the Decision OS MCP MCP Server, which means it retrieves data without modifying state.
Register the Decision OS MCP server in PolicyLayer and add a rule for list_cases: 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 Decision OS MCP. Nothing to install.
list_cases 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_cases 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_cases. 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_cases is provided by the Decision OS MCP server (marianstefi20/decision-os-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 →