Generate executable test code (Playwright or API tests) from test cases and steps
AI agents use generate_test_code to create or update resources in Decide Test MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Decide Test MCP environment.
This tool generates/creates test code files from input test cases and steps. It produces new artifacts (code files) but does not execute them - execution is handled by sibling tools like 'execute_api_test', 'execute_web_test', and 'run_generated_tests'. Creating/writing code files is a Write operation.
From the tool's definition Generate executable test code (Playwright or API tests) from test cases and steps
Attacks that exploit this kind of access
Generate executable test code (Playwright or API tests) from test cases and steps. It is categorised as a Write tool in the Decide Test MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Decide Test MCP server in PolicyLayer and add a rule for generate_test_code: 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 Decide Test MCP. Nothing to install.
generate_test_code 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 generate_test_code 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 generate_test_code. 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.
generate_test_code is provided by the Decide Test MCP server (k-n-t-lam/decide-test-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 →