Retrieve full details of specific contexts by their IDs or find related contexts. WHEN TO USE: - Getting full content after seeing previews in list_contexts - Viewing complete details from semantic_search results - Finding contexts related to a specific context - Retrieving multiple contexts at o...
AI agents call get_context 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 purely retrieves and queries existing data from a memory system without creating, modifying, deleting, or executing any operations. It is a read-only information retrieval function with no destructive or side-effect capabilities. The optional relation_type parameter only affects which data is returned, not any state changes.
From the tool's definition Tool retrieves full details of contexts by ID with parameters for querying related contexts. Description states it enables 'Retrieve full details', 'Viewing complete details', and 'Retrieving multiple contexts' with no modification or deletion capabilities.
Documented attack patterns abuse exactly the kind of access get_context 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 get_context:
{
"version": "1",
"default": "deny",
"tools": {
"get_context": {}
}
}get_context 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.
Retrieve full details of specific contexts by their IDs or find related contexts. WHEN TO USE: - Getting full content after seeing previews in list_contexts - Viewing complete details from semantic_search results - Finding contexts related to a specific context - Retrieving multiple contexts at once PARAMETERS: - context_ids: Single ID (string) or multiple IDs (array) - relation_type: Optional. Find related contexts (depends_on, related_to, fixes, implements, tests, documents) Returns complete context data: id, content, type, files, metadata, tags, timestamps. 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 get_context: 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.
get_context 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 get_context 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 get_context. 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.
get_context 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.