AI agents call list_projects to retrieve information from Memora without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward read operation that retrieves metadata about projects stored in the semantic knowledge graph. It has no side effects, does not execute code, does not modify data, and does not delete anything. The blast radius of misuse is minimal—an attacker could only learn what projects exist in the graph. This fits squarely in the Read category with low severity.
From the tool's definition Tool name 'list_projects' combined with description 'Distinct project values present in the graph' indicates a retrieval operation that queries and returns a list of existing projects from the knowledge graph without modifying, deleting, or executing anything.
Attacks that exploit this kind of access
Distinct project values present in the graph. It is categorised as a Read tool in the Memora MCP Server, which means it retrieves data without modifying state.
Register the Memora MCP server in PolicyLayer and add a rule for list_projects: 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 Memora. Nothing to install.
list_projects 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_projects 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_projects. 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_projects is provided by the Memora MCP server (vnemaidev/memora). 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 →