Plan from a natural-language task description.
AI agents invoke plan_from_text to trigger actions in PDDL MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool runs the Fast Downward planner and executes planning operations based on arbitrary natural-language input. Since it involves executing an external planner with dynamically generated PDDL, the blast radius is high — a misused or adversarially crafted input could trigger unintended planning operations, resource exhaustion, or multi-robot coordination commands.
From the tool's definition 'Plan from a natural-language task description' — converts natural language to PDDL and executes planning using the Fast Downward planner, triggering external computation and batch task execution
Attacks that exploit this kind of access
Plan from a natural-language task description. It is categorised as a Execute tool in the PDDL MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the PDDL MCP Server MCP server in PolicyLayer and add a rule for plan_from_text: 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 PDDL MCP Server. Nothing to install.
plan_from_text is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the plan_from_text 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_from_text. 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_from_text is provided by the PDDL MCP Server MCP server (nbnbtm/pddl-mcp-server). 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 →