Low Risk

codegraph_memory_get

Retrieves full memory details by ID. USE WHEN: you have a memory ID from search results and need complete content.

Part of the Codegraph server.

codegraph_memory_get is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE CODEGRAPH →

Free to start. No card required.

AI agents call codegraph_memory_get to retrieve information from Codegraph without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though codegraph_memory_get only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "codegraph_memory_get": {}
  }
}

See the full Codegraph policy for all 38 tools.

Get this rule live on your own Codegraph server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY CODEGRAPH →

View all 38 tools →

These attack patterns abuse exactly the kind of access codegraph_memory_get gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so codegraph_memory_get only ever does what you allow.

SECURE CODEGRAPH →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the codegraph_memory_get tool do? +

Retrieves full memory details by ID. USE WHEN: you have a memory ID from search results and need complete content.. It is categorised as a Read tool in the Codegraph MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on codegraph_memory_get? +

Register the Codegraph MCP server in PolicyLayer and add a rule for codegraph_memory_get: 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 Codegraph. Nothing to install.

What risk level is codegraph_memory_get? +

codegraph_memory_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit codegraph_memory_get? +

Yes. Add a rate_limit block to the codegraph_memory_get 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.

How do I block codegraph_memory_get completely? +

Set action: deny in the PolicyLayer policy for codegraph_memory_get. 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.

What MCP server provides codegraph_memory_get? +

codegraph_memory_get is provided by the Codegraph MCP server (codegraph-ai/CodeGraph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Codegraph tool call.

Deterministic rules across all 38 Codegraph tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.