AI agents call list_projects to retrieve information from Engram without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates existing projects from the SQLite database along with aggregate counts. It performs a read-only query operation with no capability to modify, delete, or execute external operations. The blast radius is minimal—at worst, it could expose project information or metadata, which is a low-severity information disclosure risk if accessed by an unauthorized agent.
From the tool's definition Tool name 'list_projects' and description 'Lista todos los proyectos que existen en la base de datos con el conteo de memorias de cada uno' (Lists all projects in the database with memory count for each).
Attacks that exploit this kind of access
Lista todos los proyectos que existen en la base de datos con el conteo de memorias de cada uno. It is categorised as a Read tool in the Engram MCP Server, which means it retrieves data without modifying state.
Register the Engram 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 Engram. 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 Engram MCP server (jacksini/engram-mcp). 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 →