set_backend_log_level_tool · Memory MCP: Risk & Policy

WHAT IT DOES

What set_backend_log_level_tool does on Memory MCP

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

WHY IT NEEDS A POLICY

Why set_backend_log_level_tool needs a policy

This tool modifies a system configuration setting (log level) but the change is fully reversible by setting it to a different level. It does not execute arbitrary code, delete data, or cause financial impact. The blast radius is minimal—incorrect log levels might affect observability or performance slightly, but the change can be undone.

From the tool's definition Tool name 'set_backend_log_level_tool' and description '设置后端日志级别（用于调试）' (set backend log level for debugging) indicates modification of system configuration state (log level), which persists until changed again.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_backend_log_level_tool Rate-limited

set_backend_log_level_tool 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": {
    "set_backend_log_level_tool": {
      "limits": [
        {
          "counter": "set_backend_log_level_tool_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 Memory MCP, so you can run agents against it safely.

FAQ

Questions about set_backend_log_level_tool

What does the set_backend_log_level_tool tool do? +

设置后端日志级别（用于调试）. It is categorised as a Write tool in the Memory 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 set_backend_log_level_tool? +

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

What risk level is set_backend_log_level_tool? +

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

Can I rate-limit set_backend_log_level_tool? +

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

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

set_backend_log_level_tool is provided by the Memory MCP server (jerryzhongj/memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.