Generate a large-app execution blueprint from a high-level goal and optional JSON spec.
AI agents use plan_goal 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.
This tool creates/generates a plan or blueprint, which is a Write operation (creating structured data/artifacts). It does not execute code, delete data, or move money. The blueprint itself is a new artifact being created in the system. Medium severity because a misused plan could influence subsequent agent workflows in potentially harmful ways, but the tool itself only produces a planning artifact.
From the tool's definition Generate a large-app execution blueprint from a high-level goal and optional JSON spec
Attacks that exploit this kind of access
Generate a large-app execution blueprint from a high-level goal and optional JSON spec. 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.
Register the MEMGRAPH- MCP server in PolicyLayer and add a rule for plan_goal: 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.
plan_goal is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the plan_goal 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.
Set action: deny in the PolicyLayer policy for plan_goal. 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.
plan_goal 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →