hooks_session-end

End current session, stop daemon, and persist state Use when native Bash hooks (via Claude Code\

SERVERHamza Agent Hub 252 SOURCEhamzachallenge3-dev/hamza-agent-hub-252

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hamza-agent-hub-252/hooks-session-end.md

WHAT IT DOES

What hooks_session-end does on Hamza Agent Hub 252

AI agents call hooks_session-end to retrieve information from Hamza Agent Hub 252 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why hooks_session-end is rated Low

Even though hooks_session-end only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs hooks_session-end safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hamza Agent Hub 252, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hooks_session-end, this is the rule to start with:

hooks_session-end Allowed

hooks_session-end is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hooks_session-end": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hamza Agent Hub 252, apply this rule, and every hooks_session-end call is checked against it from then on.

FAQ

Questions about hooks_session-end

What does the hooks_session-end tool do? +

End current session, stop daemon, and persist state Use when native Bash hooks (via Claude Code\. It is categorised as a Read tool in the Hamza Agent Hub 252 MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on hooks_session-end? +

Register the Hamza Agent Hub 252 MCP server in PolicyLayer and add a rule for hooks_session-end: 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 Hamza Agent Hub 252. Nothing to install.

What risk level is hooks_session-end? +

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

Can I rate-limit hooks_session-end? +

Yes. Add a rate_limit block to the hooks_session-end 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 hooks_session-end completely? +

Set action: deny in the PolicyLayer policy for hooks_session-end. 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 hooks_session-end? +

hooks_session-end is provided by the Hamza Agent Hub 252 MCP server (hamzachallenge3-dev/hamza-agent-hub-252). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hamza Agent Hub 252, and thousands of servers like it.

This server

All 581 Hamza Agent Hub 252 tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →