Get information about a code generation session
AI agents call get_codegen_session to retrieve information from RunAutomation MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns metadata about an existing code generation session. It performs no state changes, does not execute code or browser actions, and does not destroy data. Classification as Read is appropriate with low severity given the limited blast radius of information disclosure about an internal session.
From the tool's definition Tool description states 'Get information about a code generation session' — a retrieval operation with no data modification or side effects.
Documented attack patterns abuse exactly the kind of access get_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 get_codegen_session:
{
"version": "1",
"default": "deny",
"tools": {
"get_codegen_session": {}
}
} get_codegen_session is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get information about a code generation session. It is categorised as a Read tool in the RunAutomation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RunAutomation MCP Server MCP server in PolicyLayer and add a rule for get_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.
get_codegen_session is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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.