Create a gateway session record for a provider. NOTE: this is gateway bookkeeping (gw-* ID), not a provider-native session — Codex resume needs a real Codex UUID.
AI agents use session_create to create or update resources in LLM CLI Gateway — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LLM CLI Gateway environment.
This tool creates a new session record in the gateway system. While not destructive (records can likely be deleted/modified), it modifies system state by introducing a new session identifier.
From the tool's definition Tool name 'session_create' and description 'Create a gateway session record' indicate irreversible creation of a data record. The clarification that it creates 'gateway bookkeeping (gw-* ID)' confirms this is a write operation that persists state.
Documented attack patterns abuse exactly the kind of access session_create gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LLM CLI Gateway, and nothing reaches the server without passing your rules. This is the rule we recommend for session_create:
{
"version": "1",
"default": "deny",
"tools": {
"session_create": {
"limits": [
{
"counter": "session_create_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}session_create 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.
Create a gateway session record for a provider. NOTE: this is gateway bookkeeping (gw-* ID), not a provider-native session — Codex resume needs a real Codex UUID. It is categorised as a Write tool in the LLM CLI Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LLM CLI Gateway MCP server in PolicyLayer and add a rule for session_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 LLM CLI Gateway. Nothing to install.
session_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 session_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 session_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.
session_create is provided by the LLM CLI Gateway MCP server (llm-cli-gateway). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LLM CLI Gateway, 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.
46 LLM CLI Gateway tools catalogued and risk-classified — across an index of 43,000+ MCP servers.