Closes the specified browser session and cleans up resources. Call this when done with a session.
AI agents call end_session to permanently remove resources in Nova Act — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Ending and cleaning up a browser session is an irreversible action; once closed, the session state, cookies, and in-progress work are lost and cannot be recovered. This maps to Destructive rather than Execute because it permanently terminates a resource rather than running a task. Severity is medium since it affects only a single session and not broader data, but misuse could disrupt ongoing automation workflows.
From the tool's definition 'Closes the specified browser session and cleans up resources' — terminates and cleans up a session irreversibly
Documented attack patterns abuse exactly the kind of access end_session gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Nova Act, and nothing reaches the server without passing your rules. This is the rule we recommend for end_session:
{
"version": "1",
"default": "deny",
"hide": [
"end_session"
]
} end_session disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Closes the specified browser session and cleans up resources. Call this when done with a session. It is categorised as a Destructive tool in the Nova Act MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Nova Act MCP server in PolicyLayer and add a rule for end_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 Nova Act. Nothing to install.
end_session is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the end_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 end_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.
end_session is provided by the Nova Act MCP server (madtank/nova-act-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Nova Act, 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 Nova Act tools catalogued and risk-classified — across an index of 43,000+ MCP servers.