Start a new Copilot conversation session
AI agents use copilot-session-start to create or update resources in GitHub Copilot MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub Copilot MCP Server environment.
This tool creates a new session/conversation object, which is a reversible write operation (state creation). It does not execute code, delete data, or involve financial transactions. The blast radius is low since it only initializes a session context.
From the tool's definition Start a new Copilot conversation session
Documented attack patterns abuse exactly the kind of access copilot-session-start gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GitHub Copilot MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for copilot-session-start:
{
"version": "1",
"default": "deny",
"tools": {
"copilot-session-start": {
"limits": [
{
"counter": "copilot-session-start_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} copilot-session-start 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.
Start a new Copilot conversation session. It is categorised as a Write tool in the GitHub Copilot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GitHub Copilot MCP Server MCP server in PolicyLayer and add a rule for copilot-session-start: 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 GitHub Copilot MCP Server. Nothing to install.
copilot-session-start 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 copilot-session-start 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 copilot-session-start. 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.
copilot-session-start is provided by the GitHub Copilot MCP Server MCP server (poorgramer-zack/copilot-mcp-tool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GitHub Copilot 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.
9 GitHub Copilot MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.