AI agents call endsession as a supporting operation in Project MCP Server workflows.
The name 'endsession' suggests terminating a session, which is typically a benign state-change operation. Given the server context of managing project knowledge graphs, this likely closes a session without destructive effects. However, the empty description reduces confidence.
From the tool's definition Tool name 'endsession' with empty description. No information about side effects.
Documented attack patterns abuse exactly the kind of access endsession 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 endsession:
{
"version": "1",
"default": "deny",
"tools": {
"endsession": {
"limits": [
{
"counter": "endsession_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}endsession gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
endsession. 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 endsession: 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.
endsession 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 endsession 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 endsession. 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.
endsession 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.