Get current project memory and session state
AI agents call get_project_memory to retrieve information from MCP Memory Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves project memory and session state information. There are no indications of creation, modification, deletion, execution, or financial operations. The read-only nature and the supporting context of a memory/safety tracking system confirm this is a simple data retrieval operation with minimal blast radius if misused by an agent.
From the tool's definition Tool name 'get_project_memory' and description 'Get current project memory and session state' indicate retrieval of data without modification. The verb 'Get' and lack of any state-changing language align with Read category semantics (query, fetch, retrieve).
Attacks that exploit this kind of access
Get current project memory and session state. It is categorised as a Read tool in the MCP Memory Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Memory Server MCP server in PolicyLayer and add a rule for get_project_memory: 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 MCP Memory Server. Nothing to install.
get_project_memory 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_project_memory 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_project_memory. 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_project_memory is provided by the MCP Memory Server MCP server (keleshteri/mcp-memory). 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 →