Returns currently open technical problems and TODOs sorted by severity as a Markdown string.
AI agents call get_open_problems to retrieve information from Memex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves information from the knowledge graph without creating, modifying, deleting, or executing any operations. It functions as a pure data retrieval mechanism similar to 'get_context_briefing' or 'get_project_context'. The blast radius of misuse is minimal—an agent could retrieve information but cannot cause damage through this tool alone.
From the tool's definition Tool returns data ('Returns currently open technical problems and TODOs') with no modification or side effects. The verb 'Returns' and data retrieval pattern ('get_') confirm read-only behavior.
Documented attack patterns abuse exactly the kind of access get_open_problems gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Memex, and nothing reaches the server without passing your rules. This is the rule we recommend for get_open_problems:
{
"version": "1",
"default": "deny",
"tools": {
"get_open_problems": {}
}
}get_open_problems 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.
Returns currently open technical problems and TODOs sorted by severity as a Markdown string. It is categorised as a Read tool in the Memex MCP Server, which means it retrieves data without modifying state.
Register the Memex MCP server in PolicyLayer and add a rule for get_open_problems: 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 Memex. Nothing to install.
get_open_problems 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_open_problems 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_open_problems. 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_open_problems is provided by the Memex MCP server (stifler7/memex). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Memex, 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 Memex tools catalogued and risk-classified — across an index of 43,000+ MCP servers.