Get summary of all memories for a project, organized by type.
AI agents call get_project_summary to retrieve information from Code Graph Knowledge System without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that retrieves and summarizes project memories. It has no side effects, does not modify data, execute code, delete anything, or involve financial transactions. The verb 'Get' and the passive voice 'organized' confirm this is a data retrieval function.
From the tool's definition Tool name 'get_project_summary' and description 'Get summary of all memories for a project, organized by type' indicate a retrieval operation that queries and organizes existing data without modification.
Documented attack patterns abuse exactly the kind of access get_project_summary gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Code Graph Knowledge System, and nothing reaches the server without passing your rules. This is the rule we recommend for get_project_summary:
{
"version": "1",
"default": "deny",
"tools": {
"get_project_summary": {}
}
}get_project_summary 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.
Get summary of all memories for a project, organized by type. It is categorised as a Read tool in the Code Graph Knowledge System MCP Server, which means it retrieves data without modifying state.
Register the Code Graph Knowledge System MCP server in PolicyLayer and add a rule for get_project_summary: 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 Code Graph Knowledge System. Nothing to install.
get_project_summary 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_summary 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_summary. 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_summary is provided by the Code Graph Knowledge System MCP server (royisme/codebase-rag). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Code Graph Knowledge System, 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.
30 Code Graph Knowledge System tools catalogued and risk-classified — across an index of 43,000+ MCP servers.