plan_get_tasks · Memory Bank MCP Server MCP: Risk & Policy

WHAT IT DOES

What plan_get_tasks does on Memory Bank MCP Server

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

WHY IT NEEDS A POLICY

Why plan_get_tasks needs a policy

An AI agent can call plan_get_tasks faster than any human can review — one bad instruction and it creates or modifies resources in Memory Bank MCP Server by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

plan_get_tasks Rate-limited

plan_get_tasks 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": {
    "plan_get_tasks": {
      "limits": [
        {
          "counter": "plan_get_tasks_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 Bank MCP Server, so you can run agents against it safely.

FAQ

Questions about plan_get_tasks

What does the plan_get_tasks tool do? +

获取当前任务列表. It is categorised as a Write tool in the Memory Bank MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on plan_get_tasks? +

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

What risk level is plan_get_tasks? +

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

Can I rate-limit plan_get_tasks? +

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

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

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