List development contexts in chronological order (newest first) for browsing project history. WHEN TO USE: - Browsing recent work in a project - Reviewing what was done in a session - Getting overview of project activity WHEN NOT TO USE: - Searching for specific content → use semantic_search inst...
AI agents call list_contexts to retrieve information from DevMind 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 historical development context data without any side effects or ability to modify, delete, or execute operations. It is purely informational, designed for browsing project history and reviewing past work. The ability to filter and limit results does not change its fundamental read-only nature.
From the tool's definition Tool description explicitly states it 'List development contexts in chronological order' and 'Returns contexts with previews'. The WHEN TO USE section indicates browsing, reviewing, and getting overviews—all read operations.
Documented attack patterns abuse exactly the kind of access list_contexts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DevMind MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for list_contexts:
{
"version": "1",
"default": "deny",
"tools": {
"list_contexts": {}
}
}list_contexts is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List development contexts in chronological order (newest first) for browsing project history. WHEN TO USE: - Browsing recent work in a project - Reviewing what was done in a session - Getting overview of project activity WHEN NOT TO USE: - Searching for specific content → use semantic_search instead PARAMETERS: - project_path/session_id: Filter by project or session - limit: Max contexts (default: 20) - since: Time filter (24h, 7d, 30d, 90d) - type: Filter by context type (bug_fix, feature_add, etc.) Returns contexts with previews, sorted by creation time (newest first). It is categorised as a Read tool in the DevMind MCP MCP Server, which means it retrieves data without modifying state.
Register the DevMind MCP server in PolicyLayer and add a rule for list_contexts: 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 DevMind MCP. Nothing to install.
list_contexts 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_contexts 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_contexts. 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_contexts is provided by the DevMind MCP server (jochenyang/devmind-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DevMind MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 DevMind MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.