AI agents call startsession as a supporting operation in Project MCP Server workflows.
The name suggests initiating a session, which is typically a transient, low-impact operation. Without a description, it's unclear if it reads, writes, or executes anything significant. Based on context of sibling tools (loadcontext, endsession, buildcontext), this likely initializes a working session in the knowledge graph system — closer to a Read/Write setup action.
From the tool's definition Tool name is 'startsession'; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access startsession gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Project MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for startsession:
{
"version": "1",
"default": "deny",
"tools": {
"startsession": {
"limits": [
{
"counter": "startsession_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}startsession gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
startsession. It is categorised as a Other tool in the Project MCP Server MCP Server, which means it performs auxiliary operations.
Register the Project MCP Server MCP server in PolicyLayer and add a rule for startsession: 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 Project MCP Server. Nothing to install.
startsession is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the startsession 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 startsession. 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.
startsession is provided by the Project MCP Server MCP server (tejpalvirk/project). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Project 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.
6 Project MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.