Low Risk

memory_get_relations

Provide a list of relations from the InfraNodus memory for a given concept or entity

Single-target operation

Part of the Infranodus MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call memory_get_relations to retrieve information from Infranodus 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 memory_get_relations 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.

infranodus.yaml
tools:
  memory_get_relations:
    rules:
      - action: allow

See the full Infranodus policy for all 28 tools.

Tool Name memory_get_relations
Category Read
Risk Level Low

View all 28 tools →

Agents calling read-class tools like memory_get_relations have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the memory_get_relations tool do? +

Provide a list of relations from the InfraNodus memory for a given concept or entity. It is categorised as a Read tool in the Infranodus MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on memory_get_relations? +

Add a rule in your Intercept YAML policy under the tools section for memory_get_relations. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Infranodus MCP server.

What risk level is memory_get_relations? +

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

Can I rate-limit memory_get_relations? +

Yes. Add a rate_limit block to the memory_get_relations rule in your Intercept 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 memory_get_relations completely? +

Set action: deny in the Intercept policy for memory_get_relations. 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 memory_get_relations? +

memory_get_relations is provided by the Infranodus MCP server (infranodus-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Infranodus

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.