List sessions, optionally filtered by project.
AI agents call memcp_sessions to retrieve information from Memcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about sessions without creating, modifying, deleting, or executing operations. It is purely informational and poses minimal risk—an AI agent can only learn which sessions exist, not alter system state or access sensitive data beyond metadata visibility.
From the tool's definition Tool name 'memcp_sessions' and description 'List sessions, optionally filtered by project' indicate a query/retrieval operation with no side effects. The verb 'list' and lack of any modification language confirm read-only behavior.
Documented attack patterns abuse exactly the kind of access memcp_sessions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Memcp, and nothing reaches the server without passing your rules. This is the rule we recommend for memcp_sessions:
{
"version": "1",
"default": "deny",
"tools": {
"memcp_sessions": {}
}
}memcp_sessions 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 sessions, optionally filtered by project. It is categorised as a Read tool in the Memcp MCP Server, which means it retrieves data without modifying state.
Register the Me MCP server in PolicyLayer and add a rule for memcp_sessions: 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 Memcp. Nothing to install.
memcp_sessions 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 memcp_sessions 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 memcp_sessions. 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.
memcp_sessions is provided by the Me MCP server (maydali28/memcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Memcp, 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.
24 Memcp tools catalogued and risk-classified — across an index of 43,000+ MCP servers.