record_failure_mode · MEMGRAPH- MCP: Risk & Policy

WHAT IT DOES

What record_failure_mode does on MEMGRAPH-MCP

AI agents use record_failure_mode 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_failure_mode needs a policy

This tool creates or stores a new record in project memory (a failure pattern/bug signature). It modifies the knowledge base reversibly—the record can be updated or removed later. There is no code execution, data deletion, or financial impact.

From the tool's definition Tool description states 'Record a reusable failure pattern or bug signature' — the verb 'record' indicates creation/modification of data (a failure pattern entry) rather than retrieval, deletion, or execution of external operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

record_failure_mode Rate-limited

record_failure_mode 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_failure_mode": {
      "limits": [
        {
          "counter": "record_failure_mode_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_failure_mode

What does the record_failure_mode tool do? +

Record a reusable failure pattern or bug signature. 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_failure_mode? +

Register the MEMGRAPH- MCP server in PolicyLayer and add a rule for record_failure_mode: 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_failure_mode? +

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

Can I rate-limit record_failure_mode? +

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

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

record_failure_mode 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.