session_close_check

Run a compact non-destructive close-task check with one process snapshot and a dry-run cleanup plan. It never returns a live confirm token and never terminates processes.

Server Clean Process Ended marcelocaporale/clean-process-ended
Category Read
Risk class Low
Parameters 00 required

What session_close_check does on Clean Process Ended

AI agents call session_close_check to retrieve information from Clean Process Ended without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why session_close_check needs a policy

The tool explicitly states it is non-destructive, performs only a snapshot and dry-run plan, and never terminates processes. It purely reads and reports state without any side effects, making it a Read category tool with low severity.

From the tool's definition 'non-destructive close-task check', 'never returns a live confirm token and never terminates processes', 'dry-run cleanup plan'

Questions about session_close_check

What does the session_close_check tool do? +

Run a compact non-destructive close-task check with one process snapshot and a dry-run cleanup plan. It never returns a live confirm token and never terminates processes. It is categorised as a Read tool in the Clean Process Ended MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on session_close_check? +

Register the Clean Process Ended MCP server in PolicyLayer and add a rule for session_close_check: 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 Clean Process Ended. Nothing to install.

What risk level is session_close_check? +

session_close_check is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit session_close_check? +

Yes. Add a rate_limit block to the session_close_check 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.

How do I block session_close_check completely? +

Set action: deny in the PolicyLayer policy for session_close_check. 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.

What MCP server provides session_close_check? +

session_close_check is provided by the Clean Process Ended MCP server (marcelocaporale/clean-process-ended). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.