AI agents use create-session to create or update resources in CodeAnalysis MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CodeAnalysis MCP Server environment.
The 'create-session' action creates or initializes a session object, which is a reversible write operation. No data is destructed, executed, or moved. However, empty description and the analysis-focused context lower confidence slightly—the session could theoretically be stateless or have minimal side effects, but creation implies at least some state persistence.
From the tool's definition Tool name 'create-session' indicates data creation. Sibling tools include 'clear-session', suggesting session state management. Description is empty, limiting specificity.
Documented attack patterns abuse exactly the kind of access create-session gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CodeAnalysis MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create-session:
{
"version": "1",
"default": "deny",
"tools": {
"create-session": {
"limits": [
{
"counter": "create-session_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create-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.
create-session. It is categorised as a Write tool in the CodeAnalysis MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CodeAnalysis MCP Server MCP server in PolicyLayer and add a rule for create-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 CodeAnalysis MCP Server. Nothing to install.
create-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 create-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 create-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.
create-session is provided by the CodeAnalysis MCP Server MCP server (0xjcf/mcp_codeanalysis). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CodeAnalysis 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.
31 CodeAnalysis MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.