Create a structured test plan in Markdown format. Used by the Playwright Test Planner agent.
AI agents use test_plan_create to create or update resources in MCP Playwright Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Playwright Server environment.
This tool creates a Markdown document (a test plan). It's a write operation that produces a structured file. There are no destructive, financial, or execution side effects—it simply generates documentation. Severity is low because misuse would at most create an unwanted or incorrect test plan document.
From the tool's definition Create a structured test plan in Markdown format
Attacks that exploit this kind of access
Create a structured test plan in Markdown format. Used by the Playwright Test Planner agent. It is categorised as a Write tool in the MCP Playwright Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Playwright Server MCP server in PolicyLayer and add a rule for test_plan_create: 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 MCP Playwright Server. Nothing to install.
test_plan_create 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 test_plan_create 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 test_plan_create. 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.
test_plan_create is provided by the MCP Playwright Server MCP server (j0hanz/playwright-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 →