End a code generation session and generate the test file
AI agents use end_codegen_session to create or update resources in RunAutomation MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RunAutomation MCP Server environment.
This tool ends a session and generates (creates) a test file, which is a Write operation — it produces a new file artifact. It doesn't execute code, delete data irreversibly, or move money. The severity is medium because it writes files to the filesystem, which could overwrite existing test files if misused.
From the tool's definition End a code generation session and generate the test file
Documented attack patterns abuse exactly the kind of access end_codegen_session gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and RunAutomation MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for end_codegen_session:
{
"version": "1",
"default": "deny",
"tools": {
"end_codegen_session": {
"limits": [
{
"counter": "end_codegen_session_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} end_codegen_session 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.
Free to start. No card required.
End a code generation session and generate the test file. It is categorised as a Write tool in the RunAutomation MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RunAutomation MCP Server MCP server in PolicyLayer and add a rule for end_codegen_session: 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 RunAutomation MCP Server. Nothing to install.
end_codegen_session 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 end_codegen_session 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 end_codegen_session. 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.
end_codegen_session is provided by the RunAutomation MCP Server MCP server (tayyabakmal1/runautomation-mcpserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from RunAutomation MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
91 RunAutomation MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.