record_decision · MEMGRAPH- MCP: Risk & Policy

WHAT IT DOES

What record_decision does on MEMGRAPH-MCP

AI agents use record_decision to create or update resources in MEMGRAPH-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MEMGRAPH-MCP environment.

WHY IT NEEDS A POLICY

Why record_decision needs a policy

This tool performs a write operation that creates or stores a new decision artifact in the project's memory/orchestration system. It is reversible (decisions can be updated or superseded) and has no destructive or financial implications. The blast radius of misuse is limited to storing potentially incorrect or misleading decision documentation, which is lower severity than Execute or Destructive actions.

From the tool's definition Tool name 'record_decision' and description 'Record a high-value architectural or implementation decision' indicate it creates or stores new data (a decision record) in the project memory system, with no deletion or irreversible modification capability…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

record_decision Rate-limited

record_decision stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "record_decision": {
      "limits": [
        {
          "counter": "record_decision_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MEMGRAPH-MCP, so you can run agents against it safely.

FAQ

Questions about record_decision

What does the record_decision tool do? +

Record a high-value architectural or implementation decision. It is categorised as a Write tool in the MEMGRAPH-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on record_decision? +

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

What risk level is record_decision? +

record_decision is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit record_decision? +

Yes. Add a rate_limit block to the record_decision 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 record_decision completely? +

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

record_decision is provided by the MEMGRAPH- MCP server (mikeb317/memgraph-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.